CloudAMQP had 36 outages in the last 2 years totaling 39h 9m of downtime — averaging 1.5 incidents per month.
There were 36 CloudAMQP outages since June 9, 2025 totaling 39h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We've identified an issue in creating new clusters, when those clusters are using "copy-config" to get definitions from another cluster. Regular cluster creation still works fine.
This incident has been resolved.
We are currently investigating. Creating shared accounts work, but not dedicated. Don't trigger upgrades or plan changes if it can be avoided.
This incident has been resolved.
Our service provider for support system is partially down. We can still reach many parts of the system and critical incidents still trigger incident response. If you have issues getting to CloudAMQP support you can use our backup email address [email protected]
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating issues with delayed or missing metrics
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We've found the issues and accounts are now being processed as they should.
This incident has been resolved.
Servers in Switzerland North can experience issues due to Storage issues at the provider. We will monitor and update when we know more.
This incident has been resolved.
Between 11:00 and 13:00 UTC we had an issue with our metrics delivery pipeline so some customers might have gotten an reduced amount of metrics, in some cases even none, while some might have seen a spike om metrics being delivered to their integration. The version that caused this has been rolled back and we are now working on a fix.
This incident has been resolved.
Around 07:30 UTC we deployed a fix that cleaned up leaking message files to a batch of impacted clusters, where around 100 clusters had some message files removed. Most clusters recovered within seconds where RabbitMQ self-healed, but some clusters experienced more severe outages where manual intervention was needed. We have since rectified and informed impacted customer. We apologise for the inconvenience this has caused and are evaluating our internal processes to prevent further occurrences.
We are currently investigating this issue
The issue has been identified.
This incident has been resolved.
Logs shipped to Datadog are currently delayed.
This incident has been resolved.