CloudAMQP incident
Management Interface Unavailable - 502 Bad Gateway Response
Affected components
Update timeline
- identified Apr 02, 2026, 02:41 PM UTC
Customers are experiencing Management UI being unavailable with 502 Bad Gateway. Timeline: - 14:16 UTC -> The issue was identified - 14:30 UTC -> Recent code changes were reverted. No relationship with incident noted.
- identified Apr 02, 2026, 02:52 PM UTC
The Management UI and brokers are serving traffic normally. You can still use the Management UI by using the Broker URL and properly typing User and Password. The impact is related to our backend service logs into Management UI via CloudAMQP SSO.
- identified Apr 02, 2026, 03:07 PM UTC
We are continuing to work on a fix for this issue.
- resolved Apr 02, 2026, 03:12 PM UTC
The Management UI SSO shortcut is back to service. Impacted Clusters: All customers with clusters created more than 6 months ago Cause: Some code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up. Impact: Only the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API. Logging into the Management UI via Credentials and all Authentications Backends was functioning normally.
Looking to track CloudAMQP downtime and outages?
Pingoru polls CloudAMQP's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when CloudAMQP reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track CloudAMQP alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required