EMQX Platform Status

All Systems Operational

About This Site

Welcome to EMQX Platform's status page. Here you will find high level availability information for the EMQX Platform managed service. Visit https://cloud-intl.emqx.com/console/ to manage your deployments on EMQX Console.

EMQX Serverless Operational
EMQX Dedicated Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Mar 15, 2026

No incidents reported today.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

No incidents reported.

Mar 12, 2026
Resolved - 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.

Mar 12, 03:30 UTC
Monitoring - 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.

Mar 2, 07:49 UTC
Update - We are continuing to work on a fix for this issue.
Mar 1, 14:21 UTC
Identified - 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.

Mar 1, 14:21 UTC
Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

No incidents reported.

Mar 4, 2026

No incidents reported.

Mar 3, 2026

No incidents reported.

Mar 2, 2026
Mar 1, 2026