502: Bad gateway

The server tried to fetch something from another server — and that server failed in return. Think of it as one machine asking another for help, and getting a shrug instead.

This isn’t your fault. It’s probably not ours either. Somewhere upstream, some “clever” infrastructure coughed up a vague error instead of a proper response. Microservices, containers, load balancers… the usual suspects. None of which existed back when the web just worked.

There’s nothing for you to do but wait or try again later. Meanwhile, the rest of this site remains delightfully unentangled — you can head back to the home page or visit the sitemap to see what still works (which is most of it, because it’s simple).

Because here, at least, the gateway is always open — and blissfully monolithic.