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.
Posted Apr 16, 2025 - 17:04 UTC
Update
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.
Posted Apr 16, 2025 - 16:48 UTC
Identified
We have identified the issue and are currently working on mitigating and fixing it.
Posted Apr 16, 2025 - 15:20 UTC
Update
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Posted Apr 16, 2025 - 15:19 UTC
Update
We’re still actively looking into it. So far, it seems like this is primarily affecting some newly created services in the Frankfurt region.
Posted Apr 16, 2025 - 14:34 UTC
Investigating
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.