58 Cloudamqp incidents · Dezember 2024 — official updates, affected components, duration and resolution details.
We're investigating connectivity issues affecting some servers in Azure West Europe. We'll post an update as soon as we know more.
Connectivity to servers in southeast Asia has been restored.
Wir untersuchen Verbindungsprobleme, die einige Server in Google europe-west2 betreffen. Wir werden ein Update veröffentlichen, sobald wir mehr wissen.
Wir werden dieses Problem weiter untersuchen.
Incident ist auf Server in europe-west2-b beschränkt
GCE meldet immer noch Probleme, aber wir sehen, dass einige API-Aufrufe erfolgreich sind.
GCE hat bestätigt, dass ein Stromausfall in europe-west2-b die Störung verursacht hat. Das Stromproblem wurde gemildert, und die vollständige Wiederherstellung der betroffenen Workloads wird vorläufig bis heute 13:00 Uhr UTC erwartet. Wir beobachten weiterhin die Erholung.
Wir werden weiterhin auf weitere Probleme achten.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir untersuchen Verbindungsprobleme, die einige Server in Azure West Europe betreffen. Wir werden ein Update veröffentlichen, sobald wir mehr wissen.
Azure ist sich dieses Problems bewusst und untersucht aktiv. Wir werden ein weiteres Update veröffentlichen, sobald wir mehr wissen.
Azure hat dieses Problem erkannt. Sie haben das Problem auf die Zugänglichkeit von Speichern in der Region eingeengt. Ihre Teams führen aktiv Wiederherstellungsmaßnahmen für die betroffene Infrastruktur durch und untersuchen gleichzeitig die zugrunde liegende Ursache. Wir überwachen den Fortschritt der Erholung und arbeiten daran, die betroffenen Ressourcen wiederherzustellen.
Wir konnten die Kommunikation mit Instanzen in Azure West Europe herstellen. Die meisten Instanzen sind wieder in Betrieb. Azure hat noch einige VMs zu lösen.
Alle CloudAMQP-Instanzen sind in Azure West Europe aktiv.
**Zusammenfassung** CloudAMQP verlor die Konnektivität mit einer Teilmenge von Clustern in Azure west Europe Availability Zone 2 am 9. Oktober. Einzelne Knotencluster in AZ2 waren am stärksten von dem Vorfall betroffen. **Auswirkungen** Kunden konnten nicht auf Daten zugreifen oder Knoten verwalten, die während des Vorfalls betroffen waren. Zeitleiste der Ereignisse aus Azure. * 12:25 UTC am 09. Oktober 2026 - Wir haben dieses Problem über unsere internen Service-Überwachungsalarme identifiziert. * 12:29 UTC am 09. Oktober 2026 – Die Auswirkungen des Kunden begannen, als VM-Festplattenausfälle in der betroffenen Einheit im westeuropäischen Speicher erkannt wurden. * 2:30 UTC am 9. Oktober 2026 – Die Untersuchung identifizierte einen Verlust des Herzschlags über mehrere Speicherknoten und Fehlerdomänen, was dazu führte, dass die Speicherskalaeinheit in den Notmodus ging. 15:32 UTC am 09. Oktober 2026 - Wir haben die Storage Scale Unit aus dem Distress-Modus genommen und die Festplatten auf den betroffenen Storage-Servern isoliert, um die Wiederherstellung der verbleibenden Festplatten zu ermöglichen. Zu diesem Zeitpunkt begannen die meisten betroffenen Kunden, eine Erholung zu sehen. * 21:00 UTC am 09. Oktober 2026 - Datacenter- und Storage-Ingenieure führten den Wiederherstellungsplan auf mehreren Speicherknoten weiter aus. 23:27 UTC am 09. Oktober 2026 – Die Bemühungen, die betroffenen Speicherknoten wiederherzustellen, waren erfolgreich, und die Arbeiten zur Wiederherstellung der virtuellen Festplatten wurden fortgesetzt. Nachfolgende Wiederherstellungsmaßnahmen umfassten die Wiederherstellung und Wiederherstellung der betroffenen Speicherressourcen auf Knotenebene. * 03:00 UTC am 10. Oktober 2026 – Die Service-Funktionalität wurde wiederhergestellt und die Kundenauswirkungen wurden gemindert. **Wurzelursache** Azure hatte ein Plattformproblem, das zu Auswirkungen auf Azure Virtual Machines-Speicherplatten in der westeuropäischen Region AZ 2 führte. Betroffene Kunden haben möglicherweise Verbindungsfehler, unerwartete Neustarts oder virtuelle Maschinen erlebt, die in einen fehlerhaften Zustand in der Region geraten sind. **Resolution** Der Maschinenzugriff wurde von Azure in etwa 3 Stunden wiederhergestellt. CloudAMQP konnte die Kommunikation mit den betroffenen Knoten wiederherstellen. Wir haben weiterhin Updates von Azure überwacht, um sicherzustellen, dass Knoten nicht mehr betroffen sind.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir sehen eine gestörte Netzwerkverbindung zwischen einigen Nicht-Azure-Netzwerken und Azure UAE North (azure-arm::uaenorth), verursacht durch ein Routing-Problem bei einem Upstream-Transit-Provider. Alle Server in der Region sind aktiv und verarbeiten Nachrichten, und Überwachung, Metriken und Protokolle funktionieren wie gewohnt. Kunden, deren Clients sich aus Netzwerken verbinden, die von diesem Routing-Problem betroffen sind, können auch Verbindungszeiten sehen. Wir haben das Problem dem Anbieter gemeldet und leiten unseren eigenen Management-Traffic um ihn herum.
Routing ist wieder normal.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir untersuchen derzeit dieses Problem.
Das Problem wurde identifiziert und ein Fix wird implementiert.
Ein Fix wurde implementiert und wir überwachen die Ergebnisse.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
DigitalOcean hat derzeit Probleme mit seiner API und dem Control Panel und Sie können auf Fehler und höhere Latenz stoßen, während das Problem weiterhin besteht
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir haben verschiedene Warnungen erhalten, die uns darüber informieren, dass einige Server auf Azure West US nicht erreichbar sind. Anscheinend scheint dies spezifisch für diese region zu sein, die 25% der server betrifft.
Microsoft Azure bestätigte, dass es Netzwerkprobleme in der Region West US gab. Derzeit sind die meisten Server in Betrieb. Wir werden die nächsten Stunden überwachen.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**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 that step, after which it failed to connect to the servers it was responsible for checking. The servers themselves stayed healthy and available throughout — the monitoring process had simply lost its ability to reach them, and reported them as down. **Resolution** We identified the affected monitoring processes, confirmed the root cause in production, and deployed a fix that makes this authorization step resilient to such transient failures and able to recover automatically. After deploying, we monitored the system to confirm that notifications returned to normal. We apologize for the confusion these false notifications may have caused.
Between 17:30 and 20:00 UTC on 2026-05-30, our server monitoring system generated a large number of false "server_unreachable" alerts. Clusters were operational and healthy throughout this period — no customer data or message delivery was affected. The alerts were caused by a rolling restart of our monitoring service, during which individual monitoring workers went offline mid-cycle and lost state. This caused the workers to report connection timeouts for servers they could no longer reach — even though those servers were fully healthy. We apologize for any concern this may have caused.
This incident has been resolved.
We are investigating connectivity issues affecting some CloudAMQP instances in Azure West Europe. Affected instances may see connection failures or unexpected restarts. The root cause is an ongoing Microsoft Azure platform incident in the West Europe region (started 14:31 UTC, 23 May 2026). Microsoft is investigating.
Resolved — 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.
Since around 8pm UTC last night, some metrics are not being forwarded to legacy integration. Prometheus integrations not affected. We are investingating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
# 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 only surfaced when it tried to renew. ## Resolution On-call staff detected the failure early morning, developers helped restore the service and collector recovered at 04:05 UTC. ## Prevention * All services, both signing and collector report failed authentication attempts earlier and with higher severity * Metrics pipeline alarm thresholds was tightened so a similar drop in data triggers alarms faster.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
Still seeing slow requests, doing another investigation.
Looks like we're back at full performance now.
This incident has been resolved.
We are currently investigating this issue.
Servers in Azure West Europe can experience connection issues due to underlying issues at provider. Latest update from Azure "Current Status: We continue to investigate an availability issue caused by a subset of unhealthy backend storage infrastructure supporting Azure Virtual Machines and Azure Direct Drive in West Europe."
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
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.
We are getting indications of instances being down in Azure region westus. We are investigating the issue.
This incident has been resolved.
Servers in Azure West US 3 can experience connection issues due to underlying issues at provider. We monitor and will update when we know more.
This incident has been resolved.
There appears to be an issue regarding sending metrics to all Legacy metrics integrations. Alarms based on broker metrics also got affected. We are currently investigating the issue Prometheus based metrics (Datadog v3 etc) not affected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Broker 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, disk\) and their corresponding alarms, Notice alarms, broker availability, and the metric graphs shown in the CloudAMQP console \(these use a separate data path and continued to update normally\). ## Timeline \(UTC\) * 03:25 — broker-metrics collection begins degrading * 03:35 — ~30% of broker-metric samples missing * 03:50 — ~50% plateau * 05:25 — collector workers cycled and re-initialised * 05:35 — full throughput restored ## Root cause Broker metrics are polled from each cluster's management HTTP API by a pool of collector workers and published to an internal message bus that both the Alarms service and Metrics Integrations consume from. At 03:25 UTC this service became unresponsive without raising an error. Affected workers silently stopped polling while remaining alive to the platform, so automatic restart did not trigger. On-call staff began investigating around 05:00 UTC; force-restarting the service restored metric flow. The exact trigger has not been identified. Our focus is on ensuring the condition is detected and handled promptly if it recurs. ## What we are changing * Added metrics and alarms specific to this service, with high-urgency paging for on-call. * Reliability improvements in the service itself to detect and restart stalled work. ## What you can do CloudAMQP offers a new generation of metrics integrations based on Prometheus, with a re-engineered pipeline that does not rely on these centralised services — each server forwards data directly to your endpoint. These have been running in production for some time and have proved very reliable. * [https://www.cloudamqp.com/blog/prometheus-metrics-integrations.html](https://www.cloudamqp.com/blog/prometheus-metrics-integrations.html) * [https://www.cloudamqp.com/docs/monitoring\_metrics\_datadog\_v3.html](https://www.cloudamqp.com/docs/monitoring_metrics_datadog_v3.html) * Background: [https://www.cloudamqp.com/blog/decentralized-observability-with-open-telemetry-part-1.html](https://www.cloudamqp.com/blog/decentralized-observability-with-open-telemetry-part-1.html)
One 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.
Customers are experiencing Management UI being unavailable with 502 Bad Gateway. Timeline: - 14:16 UTC -> The issue was identified - 14:30 UTC -> Recent code changes were reverted. No relationship with incident noted.
The Management UI and brokers are serving traffic normally. You can still use the Management UI by using the Broker URL and properly typing User and Password. The impact is related to our backend service logs into Management UI via CloudAMQP SSO.
We are continuing to work on a fix for this issue.
The 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.
