HTTP 418 I'm a Teapot— What It Means, Causes & How to Fix It
This code was defined in 1998 as an April Fools' joke in RFC 2324, Hyper Text Coffee Pot Control Protocol. It is not expected to be implemented by actual HTTP servers, but it has become a beloved Easter egg.
Enter any URL to see its real HTTP response code
Common Causes
- Easter egg response from a server with a sense of humor
- API returning a joke status for fun endpoints
- Intentional use as a non-standard refusal response
How to Fix
- 1Enjoy the joke — this is an Easter egg, not a real error
- 2If unexpected, the server may be using it as a custom refusal
- 3Check if the server has a /coffee endpoint for fun
Example
GET /coffee HTTP/1.1 → 418 I'm a Teapot → "I can't brew coffee, I'm a teapot!"
Related Client Error Codes
Bad Request
401Unauthorized
402Payment Required
403Forbidden
404Not Found
405Method Not Allowed
406Not Acceptable
407Proxy Authentication Required
408Request Timeout
409Conflict
410Gone
411Length Required
412Precondition Failed
413Content Too Large
414URI Too Long
415Unsupported Media Type
416Range Not Satisfiable
417Expectation Failed
421Misdirected Request
422Unprocessable Content
423Locked
424Failed Dependency
425Too Early
426Upgrade Required
428Precondition Required
429Too Many Requests
431Request Header Fields Too Large
451Unavailable For Legal Reasons
Commonly Referenced Status Codes
The most frequently searched HTTP status codes