418 I'm a Teapot
The server refuses to brew coffee because it is, permanently, a teapot.
Description
418 I'm a Teapot is an April Fools' joke status code defined in RFC 2324 (Hyper Text Coffee Pot Control Protocol, 1998). A server may return this code to indicate that it refuses to brew coffee because it is a teapot. It was meant as a humorous joke and is not intended for use in actual HTTP implementations.
Despite being a joke, it has been adopted by many developers as a catch-all error code, a way to indicate "I refuse this request for reasons not covered by other codes," or simply as an Easter egg. Google, GitHub, and many major platforms return 418 on /teapot endpoints.
IETF considered removing 418 in 2017 but decided to preserve it due to popular demand and its cultural significance in the developer community.
Common Causes
- Developer humor or Easter egg endpoints
- API explicitly refusing a category of requests (informal use)
- Testing error handling in clients
- A real teapot that has been connected to the internet
How to Fix
- If you receive a 418 unexpectedly, check if it's being used informally to mean "forbidden" or "not supported"
- Don't use 418 in production APIs for real error cases — use 400, 403, or 422 instead
- Enjoy the joke — it's a nod to the playful spirit of early internet culture
Check your website's HTTP status code
Check now →