Skip to the content

418 I'm a teapot

An April Fools' joke from 1998 that never went away: the answer of a teapot that is asked to brew coffee. Not a real HTTP status.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110
Name in the registry
(Unused)

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

RFC 2324 described a protocol for controlling coffee pots, and said that a teapot asked to brew coffee should answer 418. Real software carries it as an Easter egg. Google has a teapot page at google.com/teapot, and many frameworks have a constant for the code. Now and then a site uses it in earnest, to turn away requests it takes for bots.

What to do about it

Smile. If it reaches you from a site you were trying to use, the site most likely took your request for an automated one.

In your own API, don't use it for real errors: clients have no idea what to do with it. The IANA registry lists 418 as unused and keeps it reserved for exactly this reason. Too much software answers to it already for the number to be given another meaning.

Not to be confused with

403 ForbiddenThe serious way of refusing a request.
429 Too Many RequestsThe serious way of telling a client to slow down.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12