CloudAMQP incident

Delay in creating new servers when using copy-config

Notice Resolved View vendor source →

CloudAMQP experienced a notice incident on October 29, 2025, lasting 34m. The incident has been resolved; the full update timeline is below.

Started
Oct 29, 2025, 05:24 PM UTC
Resolved
Oct 29, 2025, 05:58 PM UTC
Duration
34m
Detected by Pingoru
Oct 29, 2025, 05:24 PM UTC

Update timeline

  1. identified Oct 29, 2025, 05:24 PM UTC

    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.

  2. resolved Oct 29, 2025, 05:58 PM UTC

    This incident has been resolved.