https://approjects-vendor-status-watch.static.hf.space/v/cloudampq.htmlIncidents from CloudAMPQ's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/4qchs02m65cpcloudampq:2026-08-26T13:27:48.443ZWed, 26 Aug 2026 13:27:48 +0000This incident has been resolved.https://stspg.io/89jn67xc9y5jcloudampq:2026-08-24T23:52:56.879ZMon, 24 Aug 2026 23:52:56 +0000This incident has been resolved.https://stspg.io/jzsyl69sc1plcloudampq:2026-07-23T15:33:09.000ZThu, 23 Jul 2026 15:33:09 +0000This incident has been resolved.https://stspg.io/ghsz9nmdrnphcloudampq:2026-06-25T14:10:56.046ZThu, 25 Jun 2026 14:10:56 +0000**Summary** Between June 25 and June 26, our monitoring system incorrectly reported some dedicated servers as unreachable and sent "server down" notifications for servers that were in fact operating normally. This was a monitoring-side issue only — no customer servers or services were actually down, and no data or message delivery was affected. **Impact** Affected customers received one or more alerts indicating their dedicated server was down. These alerts were false positives. The servers themselves remained healthy and fully available throughout the incident. **Root cause** Before connecting to a server, our monitoring system performs a network authorization step. A defect in how one component handled a transient network hiccup could leave a monitoring process unable to complete thhttps://stspg.io/mjhjj61tkfmlcloudampq:2026-05-30T22:25:31.999ZSat, 30 May 2026 22:25:31 +0000This incident has been resolved.https://stspg.io/b5qrlyt1g5jgcloudampq:2026-05-23T16:21:47.428ZSat, 23 May 2026 16:21:47 +0000Resolved — Microsoft has confirmed that the Azure West Europe Virtual Machines incident is resolved. The impact window was 14:09–14:13 UTC on 23 May 2026, during which a limited number of customers may have experienced connection failures or unexpected Virtual Machine restarts. The Azure environment self-healed and the service has been confirmed restored. Affected CloudAMQP instances should now be operating normally.https://stspg.io/5660811530ftcloudampq:2026-05-22T03:16:44.000ZFri, 22 May 2026 03:16:44 +0000# Legacy host metrics integrations degraded Incident window: 2026-05-21 18:37 UTC – 2026-05-22 04:05 UTC \(9h 28m\) Affected service: Legacy metric integrations \(CloudWatch, Datadog, Librato, New Relic, Splunk, Stackdriver\). Host metrics affected, not broker metrics, nor was internal monitoring or console graphs. ## Summary For ~9.5 hours, the service that collects host-level metrics \(CPU, memory, disk, network\) for legacy third-party integrations entered a crash loop and stopped shipping data. ## Root Cause An internal credential-signing service was migrated to a new container runtime the afternoon before. Due to a bug with environment variables the collector could not renew it's credentials. The collector's existing credential remained valid for several hours, so the failure ohttps://stspg.io/sjzhwplndhb2cloudampq:2026-05-19T13:21:59.259ZTue, 19 May 2026 13:21:59 +0000This incident has been resolved.https://stspg.io/s5gndgw8g9qmcloudampq:2026-05-05T10:23:31.681ZTue, 05 May 2026 10:23:31 +0000This incident has been resolved.https://stspg.io/qwg5mvjw66vscloudampq:2026-05-03T19:11:24.214ZSun, 03 May 2026 19:11:24 +0000This incident has been resolved.https://stspg.io/s5vj6km0gbj9cloudampq:2026-04-28T10:27:23.381ZTue, 28 Apr 2026 10:27:23 +0000We 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.https://stspg.io/xrl3rvbjw51ccloudampq:2026-04-24T09:36:54.658ZFri, 24 Apr 2026 09:36:54 +0000This incident has been resolved.https://stspg.io/yzkt6x0627r8cloudampq:2026-04-23T10:10:49.006ZThu, 23 Apr 2026 10:10:49 +0000This incident has been resolved.https://stspg.io/cz0d0tq0vz4mcloudampq:2026-04-23T03:30:55.000ZThu, 23 Apr 2026 03:30:55 +0000Broker metrics and metrics integrations degradation Window: 2026-04-23 03:25 – 05:35 UTC \(2h 10m\) ## Impact Broker metrics \(connections, channels, queues, consumers, message rates, node and netsplit state\) were degraded, progressively dropping until recovery at 05:35 UTC. Downstream effects: * Queue, Consumer, Connection, Channel, Connection flow, and Netsplit alarms: threshold breaches during the window may not have triggered, or triggered late. Alarms already tripped before 03:25 UTC kept their state. * Metrics Integrations \(Datadog, CloudWatch, New Relic, Splunk, Dynatrace, etc.\): delivery of broker metrics was reduced for the duration of the window. Alarms configured on the receiving side may likewise have missed or lagged. Not affected: server metrics \(CPU, memory,https://stspg.io/31f87rl14lhpcloudampq:2026-04-15T14:00:00.000ZWed, 15 Apr 2026 14:00:00 +0000One of our backend components suffered a small outage due to an unexpected full services restart. Connectivity with the servers were broken and service triggered alarms for many clusters. We apologize for the inconvenience. All clusters were operational and healthy within the incident/alarms timespan.https://stspg.io/mxmty7zb5lpncloudampq:2026-04-02T14:41:09.826ZThu, 02 Apr 2026 14:41:09 +0000The Management UI SSO shortcut is back to service. Impacted Clusters: All customers with clusters created more than 6 months ago Cause: Some code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up. Impact: Only the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API. Logging into the Management UI via Credentials and all Authentications Backends was functioning normally.https://stspg.io/0r9y1ypk002zcloudampq:2026-03-25T17:45:56.264ZWed, 25 Mar 2026 17:45:56 +0000This incident has been resolved.https://stspg.io/k05dwg3nznjycloudampq:2026-03-18T21:25:45.743ZWed, 18 Mar 2026 21:25:45 +0000This incident has been resolved.https://stspg.io/4zn7wt7dtn28cloudampq:2026-03-03T21:11:20.327ZTue, 03 Mar 2026 21:11:20 +0000This incident has been resolved.https://stspg.io/gxvwrgv0z05vcloudampq:2026-03-03T18:28:21.809ZTue, 03 Mar 2026 18:28:21 +0000### Summary On March 3, an internal monitoring metric stopped being reported for approximately 14 hours. No customer metrics delivery was affected, all integrations continued operating normally. The missing metric caused our dashboards to display false failure rates, which was incorrectly reported as a metrics delivery outage. ### Impact None. Metrics continued to be delivered to all customer endpoints throughout the incident. ### Resolution The monitoring metric was restored and we have updated our alerting queries to be resilient to missing data, preventing false positives in the future.https://stspg.io/q8dksfkrv52rcloudampq:2026-03-02T05:35:34.912ZMon, 02 Mar 2026 05:35:34 +0000We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to support@cloudamqp.com if you have any questions.https://stspg.io/255qltz3mp03cloudampq:2026-03-01T13:20:55.739ZSun, 01 Mar 2026 13:20:55 +0000We are suspending active updates on this status page regarding the AWS Middle East (Bahrain/UAE) outages. We will start supporting those regions again when they have been fully recovered. Reach out to support@cloudamqp.com if you have any questions.https://stspg.io/30gtb53s227jcloudampq:2026-02-17T19:31:27.408ZTue, 17 Feb 2026 19:31:27 +0000This incident has been resolved.https://stspg.io/bktcs050d4nscloudampq:2026-02-03T14:47:54.350ZTue, 03 Feb 2026 14:47:54 +0000This incident has been resolved.https://stspg.io/j9pyf4kgnvczcloudampq:2026-02-03T02:53:23.770ZTue, 03 Feb 2026 02:53:23 +0000This incident has been resolved by Azure, https://azure.status.microsoft/en-us/statushttps://stspg.io/k1yc6m4422y7cloudampq:2026-01-14T15:54:03.856ZWed, 14 Jan 2026 15:54:03 +0000This incident has been resolved.https://stspg.io/61nw8n805f2fcloudampq:2025-12-11T12:16:32.974ZThu, 11 Dec 2025 12:16:32 +0000This incident has been resolved by third party.https://stspg.io/6gyg50fcfd3bcloudampq:2025-12-10T10:13:57.543ZWed, 10 Dec 2025 10:13:57 +0000This incident has been resolved.https://stspg.io/sy6lylfskp71cloudampq:2025-11-19T15:07:48.123ZWed, 19 Nov 2025 15:07:48 +0000This incident has been resolvedhttps://stspg.io/p04lvp7n4p62cloudampq:2025-11-17T22:52:38.569ZMon, 17 Nov 2025 22:52:38 +0000This incident has been resolved.