EMQ Technologies had 12 outages in the last 2 years totaling 705h 43m of downtime — averaging 0.5 incidents per month.
There were 12 EMQ Technologies outages since January 8, 2025 totaling 705h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have observed an availability zone disruption in GCP europe-west2-b and are investigating the impact. New deployment creation in the affected zone may fail. Existing affected deployments will fail over to other availability zones. We will continue to monitor the situation.
Between 00:31 and 00:59 UTC, an EMQX Cloud deployment in AWS us-west-2 experienced intermittent Redis request timeouts and inter-node communication errors. Message publish rate fluctuated slightly. We did not observe widespread client disconnections or node restarts, and cluster metrics are currently normal. AWS reported an underlying network issue in us-west-2 during an overlapping period. We are working with AWS to confirm its relationship to the observed errors and whether any instance-level remediation is needed. We will continue monitoring and share further findings when available.
This incident has been resolved.
We have detected network connectivity issues in the GCP us-central1 region, which may affect some EMQX Cloud services in this region. We are actively investigating the issue and monitoring the status of affected services. Further updates will be provided as more information becomes available.
The network connectivity issue affecting access to EMQX Cloud services in the GCP us-central1 region has been resolved. During the incident, connections to us-central1 from other cloud providers or geographic regions may have experienced network timeouts and packet loss. Connections within the same cloud provider and region were not affected. Service connectivity has returned to normal, and we will continue to monitor the environment to ensure stability.
We have detected AWS network issues in the us-west-2 (US West - Oregon) region, which may cause client disconnections or frequent reconnects for some services in this region. We are actively monitoring the network status and recommend that affected services check client connectivity and reconnection behavior.
AWS has completed mitigation work for the network connectivity issue affecting multiple services in the us-west-2 (US West - Oregon) region. Service connectivity is continuing to recover, with error rates and connection timeouts decreasing as network routes are restored. The issue has not yet been fully resolved. We will continue monitoring AWS recovery progress and affected EMQX Cloud services.
We are continuing to work on a fix for this issue.
AWS has confirmed that the network connectivity issue affecting multiple services in the us-west-2 (US West - Oregon) region has been fully resolved. All network routes have been restored, and AWS services are operating normally. We will continue monitoring the region and the status of affected EMQX Cloud services to ensure continued stability.
AWS has confirmed that the network connectivity issue affecting multiple services in the us-west-2 (US West - Oregon) region has been fully resolved. All network routes have been restored, and AWS services are operating normally. Our monitoring also indicates that affected EMQX Cloud services have remained stable.
We have identified an external network issue affecting some deployments hosted in Google Cloud Mumbai (asia-south1). Starting at approximately 06:30 UTC on June 19, 2026, we observed intermittent network instability impacting multiple deployments in the region. Customers may experience increased latency, packet loss, or temporary connectivity disruptions. The issue appears consistent with an ongoing Google Cloud networking incident affecting traffic originating from Mumbai and surrounding areas. We are actively monitoring the situation and will provide updates as more information becomes available. Reference: https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We continue to monitor an external network issue affecting connectivity to some deployments hosted in Google Cloud Mumbai (asia-south1). Based on current observations, the impact primarily affects cross-region traffic to Mumbai. Customers connecting from other regions, including Singapore, may experience increased latency or intermittent connectivity issues. Traffic originating within India appears to be operating normally. The issue is consistent with an ongoing Google Cloud networking incident. EMQX Cloud services remain operational, and we are closely monitoring the situation while awaiting further updates from Google Cloud.
Google Cloud has resolved the underlying network issue affecting connectivity to deployments hosted in Mumbai (asia-south1). We have continued monitoring our services following Google's recovery announcement and have observed normal network performance with no further impact. This incident is now considered resolved. Reference: https://status.cloud.google.com/incidents/5fGQt4VbkDnr3Yp8PXPr
AWS has confirmed network connectivity issues in the US-EAST-1 region affecting multiple services. While AWS reports early signs of recovery, we are observing continued network instability that may impact EMQX Cloud deployments in this region. Please ensure your MQTT clients have automatic reconnection logic enabled. Clients with proper reconnect mechanisms will automatically restore connections without data loss. Most standard MQTT client libraries have this capability built-in by default.
Additionally, data integration connectors and extended authentication services that depend on external resources in us-east-1 may experience intermittent timeout errors. This particularly affects configurations using AWS managed services such as Network Load Balancers, DynamoDB, Lambda, InfluxDB, and other endpoints hosted in the us-east-1 region.
AWS reports that recovery is progressing in the US-EAST-1 region. Their mitigations are showing early signs of success in several Availability Zones, with remaining AZs being addressed. We are observing gradual improvement in network stability and expect the intermittent connection issues to subside as AWS completes their recovery process.
The AWS US-EAST-1 region incident has been fully resolved. AWS has confirmed that all services have returned to normal operations. All EMQX Cloud services in the us-east-1 region are now operating normally. All connectivity issues have been resolved. MQTT connections, data integration connectors, and extended authentication services are functioning normally. We have re-enabled new resource provisioning in the us-east-1 region.
We are currently investigating this issue.
We have implemented mitigation measures and client connection stability has improved. We continue to monitor the situation closely to ensure full resolution.
We are continuing to monitor for any further issues.
The issue has been fully resolved. All Asia-Pacific Serverless cluster connections are now operating normally. We will continue routine monitoring to prevent recurrence.
At 01:56 UTC on July 17, 2025, we detected a partial node failure in the Serverless cluster in the US region due to underlying instance issues. We immediately initiated a failover process to replace the affected nodes. During the failover, some clients connected to the impacted nodes may experience brief disconnections. However, client reconnections are not affected, and services are expected to recover automatically. We are closely monitoring the situation and will provide further updates as needed.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
By 02:09 UTC, the failover was successfully completed. Based on continued monitoring, we confirm that the Serverless cluster has fully recovered and is operating normally. We appreciate your patience and understanding.
We are currently monitoring an incident affecting EMQX Cloud deployments on the GCP platform. Due to an upstream issue reported by Google Cloud (https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW), creating new deployments on GCP has been temporarily restricted since 19:06 UTC on June 12, 2025. Existing deployments are not affected and continue to operate normally. We are actively monitoring the situation and will provide updates as soon as the issue is resolved by the upstream provider. Thank you for your understanding.
We have also observed that, in addition to deployment creation issues, EMQX Cloud data forwarding to GCP-related integration services and external authentication systems is being affected by the ongoing GCP outage. This includes, but is not limited to: * GCP Pub/Sub * GCP Cloud PostgreSQL * Other GCP-hosted services used for external authentication or extensions We strongly recommend that affected customers review the status of their data integrations and external authentication endpoints to ensure continued reliability. We will continue monitoring the situation and provide updates as necessary.
The earlier issue caused by a Google Cloud Platform (GCP) outage (https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW) has now been resolved. We have verified that: New deployments on the GCP platform are now functioning normally. Data integration forwarding to GCP services such as Cloud Pub/Sub, Cloud PostgreSQL, and external authentication systems is also operating as expected. If you experienced any issues during the incident, we recommend reviewing your data pipelines and integrations to ensure they have fully recovered. Thank you for your patience while we monitored this issue.
We have detected an issue with GCP Pub/Sub causing timeout failures for some customers' data integrations when forwarding to GCP Pub/Sub. For further details, please refer to the GCP Pub/Sub outage report. https://status.cloud.google.com/incidents/ghMho2Gka33Exr9UNavz If the GCP Pub/Sub action in the data integration is a synchronous forward, the timeout on GCP Pub/Sub may result in a timeout for client message publishing. We recommend customers to check if their business is affected.
We are continuing to monitor for any further issues.
The issue with GCP Pub/Sub that caused timeout failures for some customers' data integrations when forwarding to GCP Pub/Sub has been resolved. No further timeout issues have been observed with deployments. For further details, you can refer to the GCP Pub/Sub outage