All HTTP status codes

HTTP 418 I'm a teapot

Client Error

An April Fools' joke from the Hyper Text Coffee Pot Control Protocol: the server is a teapot and refuses to brew coffee. Some real services use it as a playful block response.

Defined in RFC 2324 (April 1st)

Common causes

  • Easter-egg endpoints
  • Some services returning it for blocked/bot traffic

How to fix it

  1. Treat it as a non-standard client error; check the service's docs for the real meaning

Related status codes

403 Forbidden

The server understood the request and refuses to authorize it. Unlike 401, re-authenticating won't help — the identity is known but lacks permission.

400 Bad Request

The server can't or won't process the request because the client sent something malformed — invalid JSON, bad query parameters, broken headers or framing.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.