EMQ Technologies Outage History

Started Oct 20, 2026, 06:56 AM UTC· resolved Oct 20, 2026, 07:02 AM UTC

1. investigating Oct 20, 2026, 06:56 AM UTC

   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.

Read the full incident report →

Started Sep 27, 2026, 03:48 AM UTC· resolved Sep 27, 2026, 02:51 PM UTC

1. monitoring Sep 27, 2026, 03:48 AM UTC

   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.

2. resolved Sep 27, 2026, 02:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 02:45 PM UTC· resolved Sep 01, 2026, 04:00 PM UTC

1. investigating Sep 01, 2026, 03:20 PM UTC

   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.

2. resolved Sep 01, 2026, 04:54 PM UTC

   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.

Read the full incident report →

Started Jul 24, 2026, 11:35 AM UTC· resolved Jul 24, 2026, 01:45 PM UTC

1. investigating Jul 24, 2026, 11:35 AM UTC

   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.

2. identified Jul 24, 2026, 12:41 PM UTC

   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.

3. identified Jul 24, 2026, 12:41 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Jul 24, 2026, 01:09 PM UTC

   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.

5. resolved Jul 24, 2026, 01:45 PM UTC

   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.

Read the full incident report →

Started Jun 19, 2026, 06:57 AM UTC· resolved Jul 06, 2026, 07:08 AM UTC

1. investigating Jun 19, 2026, 06:57 AM UTC

   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

2. identified Jun 19, 2026, 06:57 AM UTC

   The issue has been identified and a fix is being implemented.

3. identified Jun 19, 2026, 07:02 AM UTC

   We are continuing to work on a fix for this issue.

4. identified Jun 19, 2026, 07:04 AM UTC

   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.

5. resolved Jul 06, 2026, 07:08 AM UTC

   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

Read the full incident report →

Started May 29, 2026, 08:07 AM UTC· resolved May 30, 2026, 12:32 AM UTC

1. identified May 29, 2026, 08:07 AM UTC

   We have detected elevated network and infrastructure-related alerts affecting some EMQX Cloud deployments in the Azure West US 2 region. Customers with deployments in this region may experience increased latency, intermittent connectivity, or connection timeouts when accessing EMQX Cloud services. According to Azure’s service health update, the issue is related to a power event impacting underlying infrastructure in the West US 2 region. We are continuously monitoring the affected EMQX Cloud services and Azure’s mitigation progress. For more information, please refer to the Azure status page: https://azure.status.microsoft/en-us/status We will continue to monitor the situation and provide updates as progress is made. Thank you for your understanding.

2. monitoring May 29, 2026, 02:35 PM UTC

   Azure has provided an update indicating significant improvements following the power event that impacted underlying datacenter infrastructure in the West US 2 region. Several dependent Azure services have recovered, including Azure Kubernetes Service, Azure Storage, Azure Monitor, Log Analytics, Azure Container Registry, and other infrastructure services. We are continuing to observe service recovery for affected EMQX Cloud deployments in this region and are monitoring service health closely. Customers may still experience intermittent latency or connectivity issues while Azure continues mitigation efforts for remaining affected services. For more information, please refer to the Azure status page: https://azure.status.microsoft/en-us/status We will continue to monitor the situation and provide updates as progress is made. Thank you for your understanding.

3. resolved May 30, 2026, 12:32 AM UTC

   The service degradation affecting some EMQX Cloud deployments in the Azure West US 2 region has been resolved. According to Azure’s latest update, the underlying Azure service disruption occurred between 04:24 UTC and 20:18 UTC on 29 May 2026 and was caused by severe weather in the region, including lightning strikes, which resulted in utility power loss and related cooling issues across multiple datacenter buildings. During the incident, customers with EMQX Cloud deployments in this region may have experienced increased latency, intermittent connectivity, connection timeouts, elevated error rates, or temporary service accessibility issues. Azure has confirmed that power has been fully restored and that the remaining affected services have recovered after continued monitoring. We have also observed that affected EMQX Cloud services in this region have returned to normal operation. For more information, please refer to the Azure status page: https://azure.status.microsoft/en-us/status We apologize for any inconvenience caused and thank you for your patience and understanding.

Read the full incident report →

Started Mar 01, 2026, 02:21 PM UTC· resolved Mar 12, 2026, 03:30 AM UTC

1. identified Mar 01, 2026, 02:21 PM UTC

   Due to a localized power issue affecting a single Availability Zone (mec1-az2) in the AWS ME-CENTRAL-1 (UAE) Region, multiple AWS services are experiencing increased error rates, connectivity interruptions, and latency. Affected services may include EC2, EBS, RDS, and other dependent infrastructure components within the impacted Availability Zone. Impact 1. Resources running in mec1-az2 may be unavailable or experience connectivity issues. 2. Increased API error rates and latency for workflows tied to the affected AZ. 3. New deployments in the UAE region are temporarily suspended. Mitigation Actions 1. We have completed failover procedures for impacted customer deployments where possible. 2. Traffic has been shifted away from the affected Availability Zone. 3. Deployments in other Availability Zones within ME-CENTRAL-1 remain operational. Customer Action Required 1. Review any external dependencies (e.g., load balancers, DNS records, NAT gateways, third-party integrations) to ensure traffic is directed to healthy Availability Zones. 2. Confirm redundancy configurations are functioning as expected. 3. Avoid launching new workloads in the UAE region until further notice.

2. identified Mar 01, 2026, 02:21 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Mar 02, 2026, 07:49 AM UTC

   Summary AWS has confirmed an additional localized power issue affecting Availability Zone mec1-az3 in the ME-CENTRAL-1 (UAE) Region. At this time, only mec1-az1 remains operational for existing workloads. New instance launches in the region are currently not possible. Multiple AWS services, including EC2, S3, and DynamoDB, are experiencing elevated error rates and latency. Current Situation 1. mec1-az2 and mec1-az3 are unavailable 2. mec1-az1 remains operational for existing instances 3. Region-wide instance launches are currently failing 4. Cross-service API error rates remain elevated Mitigation Actions 1. We have completed failover procedures and migrated affected deployments to the remaining healthy Availability Zone. 2. All impacted workloads have been stabilized under a single-AZ operational mode. 3. Once additional Availability Zones are restored, we will rebuild the multi-AZ high-availability cluster architecture. Operational Mode At this stage, deployments in the UAE region are running in temporary single-AZ mode. High availability across multiple Availability Zones will be restored once AWS confirms recovery. Next Update We continue to monitor AWS recovery efforts closely and will provide further updates as soon as additional Availability Zones become available.

4. resolved Mar 12, 2026, 03:30 AM UTC

   Update - UAE Region Decommissioned Following the recent infrastructure disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), and due to the continued Availability Zone instability with no confirmed recovery timeline from AWS, EMQX Cloud has completed a controlled decommission of the UAE region. As part of our risk mitigation and service continuity measures, all customer deployments previously hosted in the UAE region have been successfully migrated to alternative AWS regions. Current Status 1. All affected deployments have been migrated to other healthy AWS regions. 2. No customer service interruption has been observed during the migration process. 3. The UAE region is no longer available for new deployments. Operational Note This action was taken to ensure service stability and avoid potential future disruptions related to the ongoing infrastructure situation in the region. Next Steps We will continue to monitor the AWS recovery progress for the ME-CENTRAL-1 region. Any future reintroduction of UAE regional capacity will be evaluated after AWS confirms full infrastructure recovery and regional stability.

Read the full incident report →

Started Oct 20, 2025, 02:55 PM UTC· resolved Oct 21, 2025, 12:48 AM UTC

1. investigating Oct 20, 2025, 02:55 PM UTC

   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.

2. identified Oct 20, 2025, 04:01 PM UTC

   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.

3. monitoring Oct 20, 2025, 06:08 PM UTC

   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.

4. resolved Oct 21, 2025, 12:48 AM UTC

   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.

Read the full incident report →

Started Oct 07, 2025, 12:40 PM UTC· resolved Oct 07, 2025, 01:37 PM UTC

1. investigating Oct 07, 2025, 12:40 PM UTC

   We are currently investigating this issue.

2. monitoring Oct 07, 2025, 01:06 PM UTC

   We have implemented mitigation measures and client connection stability has improved. We continue to monitor the situation closely to ensure full resolution.

3. monitoring Oct 07, 2025, 01:06 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 07, 2025, 01:37 PM UTC

   The issue has been fully resolved. All Asia-Pacific Serverless cluster connections are now operating normally. We will continue routine monitoring to prevent recurrence.

Read the full incident report →

Started Jul 17, 2025, 02:02 AM UTC· resolved Jul 17, 2025, 02:56 AM UTC

1. investigating Jul 17, 2025, 02:02 AM UTC

   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.

2. identified Jul 17, 2025, 02:03 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 17, 2025, 02:09 AM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jul 17, 2025, 02:49 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 17, 2025, 02:56 AM UTC

   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.

Read the full incident report →

Started Jun 12, 2025, 07:45 PM UTC· resolved Jun 12, 2025, 09:24 PM UTC

1. identified Jun 12, 2025, 07:45 PM UTC

   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.

2. identified Jun 12, 2025, 07:51 PM UTC

   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.

3. resolved Jun 12, 2025, 09:24 PM UTC

   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.

Read the full incident report →

Started Jan 08, 2025, 04:41 PM UTC· resolved Jan 08, 2025, 04:44 PM UTC

1. monitoring Jan 08, 2025, 04:41 PM UTC

   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.

2. monitoring Jan 08, 2025, 04:43 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jan 08, 2025, 04:44 PM UTC

   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

Read the full incident report →