EMQ Technologies Outage History

EMQ Technologies is up right now

EMQ Technologies had 7 outages in the last 2 years totaling 691h 59m of downtime — averaging 0.3 incidents per month.

There were 7 EMQ Technologies outages since October 7, 2025 totaling 691h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.emqxcloud.com

Notice September 1, 2026

Network Issues in GCP us-central1 Region

Detected by Pingoru
Sep 01, 2026, 02:45 PM UTC
Resolved
Sep 01, 2026, 04:00 PM UTC
Duration
1h 15m
Affected: EMQX DedicatedFlex
Timeline · 2 updates
  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 →

Minor July 24, 2026

AWS Network Issues in us-west-2 Region

Detected by Pingoru
Jul 24, 2026, 11:35 AM UTC
Resolved
Jul 24, 2026, 01:45 PM UTC
Duration
2h 9m
Affected: EMQX DedicatedFlex
Timeline · 5 updates
  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 →

Minor June 19, 2026

GCP Mumbai (asia-south1) Network Connectivity Issues

Detected by Pingoru
Jun 19, 2026, 06:57 AM UTC
Resolved
Jul 06, 2026, 07:08 AM UTC
Duration
17d
Affected: EMQX DedicatedFlex
Timeline · 5 updates
  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 →

Minor October 20, 2025

AWS US-East-1 Network Instability

Detected by Pingoru
Oct 20, 2025, 02:55 PM UTC
Resolved
Oct 21, 2025, 12:48 AM UTC
Duration
9h 52m
Affected: EMQX ServerlessEMQX DedicatedFlex
Timeline · 4 updates
  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 →

Minor October 7, 2025

Asia-Pacific Serverless Cluster Connectivity Issues

Detected by Pingoru
Oct 07, 2025, 12:40 PM UTC
Resolved
Oct 07, 2025, 01:37 PM UTC
Duration
56m
Affected: EMQX Serverless
Timeline · 4 updates
  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 →