IETF draft proposes HTTP status code 483 'I'm Not a Freezer'
An Internet-Draft submitted independently to the IETF by R. Bánffy proposes a new HTTP status code, 483, labeled 'I'm Not a Freezer.' The code would be returned when a server understands a request requiring freezing or refrigeration capabilities but cannot provide them. The draft also attempts to distinguish between freezers, refrigerators, low-temperature servers, frozen software processes, and services marketed as 'cold storage.'
GoKawiil's interpretation of the reporting above, not reported fact.
This is an Independent Submission Internet-Draft, a category the IETF uses for informational or whimsical documents that do not represent official IETF consensus, so it carries no standards weight on its own. It follows a long tradition of satirical HTTP status codes, such as the well-known 418 'I'm a teapot,' which play on ambiguity in protocol terminology for humorous effect rather than practical implementation.
- The draft proposes HTTP status code 483, 'I'm Not a Freezer'
- It is an Independent Submission, not an official IETF standards-track document
- It continues the tradition of joke HTTP codes similar to the 'teapot' status 418
Source: datatracker.ietf.org, 2026-11-15
Published there as: “The Hypertext Transfer Protocol Status Code 483 (I'm Not a Freezer)”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.