58 Cloudamqp incidents · dicembre 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.
Stiamo indagando su problemi di connettività che interessano alcuni server in Google europe-west2. pubblicheremo un aggiornamento non appena ne sapremo di più.
Stiamo continuando a indagare su questo problema.
L'incidente è limitato ai server in europe-west2-b
GCE sta ancora segnalando problemi, ma stiamo vedendo alcune chiamate API successo.
GCE ha confermato che un'interruzione di corrente in europe-west2-b ha causato la rottura. Il problema di potenza è stato mitigato, e il pieno recupero dei carichi di lavoro colpiti è provvisoriamente previsto entro le 13:00 UTC oggi. Continuiamo a monitorare il recupero.
Stiamo continuando a monitorare eventuali ulteriori problemi.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo indagando su problemi di connettività che interessano alcuni server in Azure West Europe. pubblicheremo un aggiornamento non appena ne sapremo di più.
Azure è a conoscenza di questo problema e stanno attivamente indagando. Posteremo un altro aggiornamento non appena ne sapremo di più.
Azure ha identificato questo problema. Hanno ridotto il problema all'accessibilità di stoccaggio che interessa la regione. I loro team stanno attivamente eseguendo azioni di recupero sull'infrastruttura interessata, continuando a indagare sulla causa sottostante. Stiamo monitorando i progressi del recupero e lavorando per ripristinare le risorse colpite.
Siamo riusciti a stabilire una comunicazione con le istanze nell'Europa occidentale di Azure. La maggior parte delle istanze sono di nuovo in funzione. Azure ha ancora alcune VM da risolvere.
Tutte le istanze CloudAMQP sono in funzione in Azure West Europe.
# Sommario # CloudAMQP ha perso la connettività con un sottoinsieme di cluster in Azure zona di disponibilità Europa occidentale 2 il 9 ottobre. I singoli cluster di nodi in AZ2 sono stati maggiormente influenzati dall'incidente. # Impatto # I clienti non sono stati in grado di accedere a dati o nodi mange influenzati durante l'incidente. Timeline degli eventi di Azure. * 12:25 UTC il 09 ottobre 2026 – Abbiamo identificato questo problema tramite i nostri avvisi di monitoraggio del servizio interno. * 12:29 UTC il 09 ottobre 2026 – L'impatto del cliente è iniziato, con i guasti del disco VM rilevati nell'unità di scala di archiviazione dell'Europa occidentale interessata. * 2:30 UTC il 09 ottobre 2026 – L'indagine ha identificato la perdita di battito cardiaco attraverso più nodi di archiviazione e domini di errore, con conseguente unità di scala di archiviazione per andare in modalità distress. * 15:32 UTC il 09 ottobre 2026 - Abbiamo preso l'unità di scala di archiviazione dalla modalità di soccorso, isolando i dischi sui server di archiviazione impattati per consentire il recupero dei dischi rimanenti. In questa fase, la maggior parte dei clienti interessati ha iniziato a vedere il recupero. * 21:00 UTC il 09 ottobre 2026 - Gli ingegneri Datacenter e Storage hanno continuato a eseguire il piano di recupero su più nodi di archiviazione. * 23:27 UTC il 09 ottobre 2026 – Gli sforzi per recuperare i nodi di archiviazione interessati hanno avuto successo, e il lavoro per recuperare i dischi virtuali ha continuato. Le successive azioni di recupero comprendevano il recupero a livello nodo e il ripristino delle risorse di stoccaggio colpite. * 03:00 UTC il 10 ottobre 2026 – Funzionalità di servizio recuperato, e l'impatto del cliente è stato mitigato. "Root cause" Azure ha sperimentato un problema della piattaforma ha portato ad un impatto sui dischi di stoccaggio Azure Virtual Machines nella regione dell'Europa occidentale AZ 2. I clienti affetti possono aver sperimentato guasti di connettività, riavviamenti inaspettati, o macchine virtuali che entrano in uno stato fallito nella regione. # Risoluzione # L'accesso alla macchina è stato ripristinato da Azure in circa 3 ore. CloudAMQP è stato in grado di ripristinare la comunicazione con i nodi impattati. Abbiamo continuato a monitorare gli aggiornamenti da Azure per garantire che i nodi non fossero più influenzati.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo vedendo la connettività di rete degradata tra alcune reti non-Azure e Azure UAE North (azure-arm::uaenorth), causata da un problema di routing a un fornitore di transito a monte. Tutti i server della regione sono aggiornati e elaborano messaggi, e il monitoraggio, metriche e registri stanno funzionando come normale. I clienti i cui clienti si connettono da reti interessate da questo problema di routing possono anche vedere timeout di connessione. Abbiamo segnalato il problema al fornitore e stanno routing il nostro traffico di gestione intorno a esso.
La routine e' tornata alla normalita'.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Stiamo attualmente indagando su questo problema.
Il problema è stato identificato e si sta attuando una correzione.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
DigitalOcean sta attualmente sperimentando problemi con la sua API e il pannello di controllo e si può eseguire in errori e latenza maggiore mentre il problema persiste
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo ricevuto diversi avvisi che ci informano su un paio di server schierati a Azure negli Stati Uniti d'America non raggiungibili. Apparentemente questo sembra essere collegato specifico a questa regione che ha un impatto del 25% dei server.
Microsoft Azure ha confermato che stavano avendo problemi di rete nella regione degli Stati Uniti. Per ora, la maggior parte dei server sono operativi. Continueremo il monitoraggio per le ore successive.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
