Intermittent 502s have been reported on some services

This incident has been resolved.

We’ve rolled out a mitigation that’s successfully cleared up all the 502s tied to this specific incident. Things are looking stable so far, but we’re still monitoring and working on a more permanent fix.

We’re still working on a fix and starting to see some improvements from the mitigation steps we’ve taken. We're now focusing on putting a more solid, permanent solution in place and will update this status page as soon as we’ve got more to share.

We have identified the issue and are currently working on mitigating and fixing it.

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

We’re still actively looking into it. So far, it seems like this is primarily affecting some newly created services in the Frankfurt region.

Some services — mostly in the Frankfurt region — have been reported to return 502s on certain requests. It’s not hitting all services, and we can’t confirm yet if it’s limited to just one region.

We’re on it and investigating.