418 I'm a teapot
A teapot refuses to brew coffee. It's a joke code, and a server using it is usually telling you, humorously, that it won't handle your request.
Quick checks
- If you see it on a real site, you may have been flagged as a bot. Slow down, turn off the VPN and try again.
If you’re visiting the site
If a site answers 418
- Some sites return 418 to block automated traffic; disable browser automation, unusual extensions or VPNs.
If you run the site
History
- RFC 2324 (1 April 1998) defined the Hyper Text Coffee Pot Control Protocol, where 418 means a teapot was asked to brew coffee.
- RFC 9110 (2022) reserves 418 as unused so it's never given a real meaning, which keeps the joke safe.
Should you use it?
- For Easter eggs, sure. For real errors, use a standard code (403, 429) so clients behave correctly.
Still not working?
Nothing to escalate: if a real service answers 418 for normal use, it's a deliberate block or a joke; contact the site if you need access.
See what’s happening
LightAtom's connections view shows which server answered, if you're curious which service is joking with you.
Frequently asked questions
Is 418 I'm a teapot a real status code?
It began as an April Fools' joke in RFC 2324 (1998). It's not part of standard HTTP, but RFC 9110 reserves the number, and many frameworks include it.
Why do some websites return 418?
As an Easter egg, or to reject bots and scrapers with a memorable response. Google once had a teapot page at google.com/teapot.
What should a client do with 418?
Treat it like any other 4xx: the request won't succeed as it is. Don't retry in a loop.