Resolved on July 23, 2025.
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.
Update timeline
- resolved Jul 23, 2025, 09:33 PM UTC
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.
Your product runs on more than CloudAMQP
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services