CloudAMQP incident

Backend slow/unresponsible

Minor Resolved View vendor source →

CloudAMQP experienced a minor incident on June 10, 2025 affecting Backend and Heroku, lasting 7h 6m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2025, 04:29 PM UTC
Resolved
Jun 10, 2025, 11:35 PM UTC
Duration
7h 6m
Detected by Pingoru
Jun 10, 2025, 04:29 PM UTC

Affected components

BackendHeroku

Update timeline

  1. investigating Jun 10, 2025, 04:29 PM UTC

    We are currently experiencing issues with our backend services handling account and server creation, and metrics collection. This does not affect any running customer servers. This is due to ongoing Heroku service disruption (affecting Heroku's dyno connectivity, Dashboard, and API). Read more about the incident here: https://status.heroku.com/incidents/2822 Reach out to [email protected] if you need help with any actions in the CloudAMQP Console/API.

  2. investigating Jun 10, 2025, 08:39 PM UTC

    https://status.heroku.com/incidents/2822

  3. monitoring Jun 10, 2025, 11:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 10, 2025, 11:35 PM UTC

    This incident has been resolved.