I see what kind of day it is going to be...

For the record... I almost certainly put the code in using that status. So yeah it's all my fault.

@N00bPancakes I think we also have 418 as a possible response status in the public api of the product I work on in production... It was supposed to be there only until my senior told me what status code should actually be returned, cause no 4xx just didn't seem right there. Don't think it ever got updated...

I have this in production code aswell. It's the status on an unspecified error. Everything that can go wrong gives an specific error and status though so it should never be reached. It still gives a JSON response with the unspecified error message.
Still would not implement it in customer/partner facing code though.

@hjk101 yeah it is my "somehow you got this far and still dorked it up".