← Back to status codes
HTTP Status Code
418 I'm a teapot
Client ErrorThe server refuses the attempt to brew coffee with a teapot. This is an Easter egg status code from an April Fools' RFC.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 418 I'm a teapot mean?
HTTP 418 I'm a teapot is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 418 I'm a teapot usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 418 I'm a teapot
HTTP example
HTTP/1.1 418 I'm a teapot
Common causes
- Intentional joke response
- RFC Easter egg implementation
- Playful API or debug behavior
How to fix it
- Do not treat it as a normal production status
- Check server logic if it appears unexpectedly
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
HTTP 418 is famous among developers, but it is not a status you should rely on in production APIs.