Live / CloudAMQP / Incident
CloudAMQP: Degraded management connectivity to Azure UAE North
CloudAMQP · cloudamqp.comResolved2026-10-06 15:48 UTC
Public — what happened
Summary
CloudAMQP said that on 2026-10-06 at 14:37 UTC it saw weakened network links between certain outside networks and its Azure UAE North region, which affected its ability to manage servers there. The company attributed the issue to a routing fault at an upstream transit provider and said servers in the region kept running and handling messages, with monitoring, metrics and logs unaffected, though customers connecting from impacted networks might experience timeouts. CloudAMQP said it reported the fault to the provider and redirected its own management traffic, and the incident was marked resolved at 15:48 the same day.
Timeline
- Started — 2026-10-06 14:37 UTC
- Identified — 2026-10-06 14:37 UTC
- Resolved — 2026-10-06 15:48 UTC · 1h 11m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach CloudAMQP against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for CloudAMQP: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the CloudAMQP report →
More from CloudAMQP
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.