Update - We are still experiencing issues with all AZ's in this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.
Mar 02, 2026 - 20:19 UTC
Update - We are continuing to monitor. The outage is in regards to the AZ mec1-az2
Mar 02, 2026 - 01:46 UTC
Update - We are continuing to monitor for any further issues.
Mar 01, 2026 - 13:23 UTC
Update - We are continuing to monitor for any further issues.
Mar 01, 2026 - 13:22 UTC
Monitoring - AWS has an ongoing issue with multiple services in region me-central-1.
Mar 01, 2026 - 13:20 UTC
Update - We are still experiencing issues with this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.
Mar 02, 2026 - 20:19 UTC
Monitoring - AWS has an ongoing issue with multiple services in region me-south-1.
Shared server hummingbird-01 affected.

Mar 02, 2026 - 05:35 UTC
Shared servers Operational
Dedicated servers Operational
Backend Operational
Metrics Operational
90 days ago
99.98 % uptime
Today
Heroku Operational
DNS Operational
Help Scout Email Processing Operational
AWS Partial Outage
90 days ago
99.29 % uptime
Today
AWS ec2-ap-northeast-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-us-west-2 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-us-west-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-us-east-2 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-us-east-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-sa-east-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-west-3 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-west-2 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-west-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-central-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ca-central-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ap-southeast-2 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ap-southeast-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ap-northeast-2 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-me-south-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-south-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-eu-north-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ap-south-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-ap-east-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-af-south-1 Operational
90 days ago
100.0 % uptime
Today
AWS ec2-me-central-1 Partial Outage
90 days ago
70.48 % uptime
Today
Google Cloud Platform Google Compute Engine Operational
90 days ago
100.0 % uptime
Today
DigitalOcean Operational
90 days ago
100.0 % uptime
Today
DigitalOcean AMS2 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean AMS3 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean FRA1 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean LON1 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean NYC2 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean NYC3 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean SFO1 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean SGP1 Operational
90 days ago
100.0 % uptime
Today
DigitalOcean TOR1 Operational
90 days ago
100.0 % uptime
Today
Microsoft Azure Operational
90 days ago
99.92 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Scheduled Maintenance

Shared RabbitMQ servers upgrade Jan 31, 2026 01:20 - Feb 23, 2026 09:20 UTC

Scheduled - Shared RabbitMQ servers are being updated to version 4.2.x.

If you are using JavaScript with amqplib/amqp-client.js, upgrade to version 10.7+/3.2.1+. RabbitMQ 4.1/2 introduces a new frame_max behavior that may cause compatibility issues.

Jan 30, 2026 - 20:26 UTC
Apr 14, 2026

No incidents reported today.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

No incidents reported.

Apr 9, 2026

No incidents reported.

Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026
Completed - The scheduled maintenance has been completed.
Apr 6, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 6, 21:00 UTC
Scheduled - We will be undergoing maintenance on some shared servers at this time
Mar 29, 23:15 UTC
Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026
Resolved - 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.

Apr 2, 15:12 UTC
Update - We are continuing to work on a fix for this issue.
Apr 2, 15:07 UTC
Update - 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.

Apr 2, 14:52 UTC
Identified - 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.

Apr 2, 14:41 UTC
Apr 1, 2026

No incidents reported.

Mar 31, 2026

No incidents reported.