CloudAMQP incident

Backend slow/unresponsible

Major Resolved View vendor source →

CloudAMQP experienced a major incident on April 28, 2026 affecting Backend, lasting 37m. The incident has been resolved; the full update timeline is below.

Started
Apr 28, 2026, 10:27 AM UTC
Resolved
Apr 28, 2026, 11:05 AM UTC
Duration
37m
Detected by Pingoru
Apr 28, 2026, 10:27 AM UTC

Affected components

Backend

Update timeline

  1. investigating Apr 28, 2026, 10:27 AM UTC

    We are currently experiencing issues with our backend services handling account and server creation. This does not affect any running customer servers but might delay provisioning new servers.

  2. identified Apr 28, 2026, 10:49 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 28, 2026, 10:53 AM UTC

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

  4. resolved Apr 28, 2026, 11:05 AM UTC

    We had an abnormal increase in traffic causing timeouts and slow responses for customer.cloudamqp.com, we increased capacity and are back to normal. This did not affect any running clusters, just provisioning and configuration updates.