Middle East Availability - AWS

Incident Report for Neo4j Aura

Postmortem

What Happened

On March 1, at 12:51 PM UTC, AWS services in the ME-CENTRAL-1 & ME-SOUTH-1 Region were impacted. Connectivity and power issues affected APIs and AWS core services essential to run Neo4j Aura prompting AWS to initiate an investigation

How the service was affected

Operations (clone, backup, resuming/pausing, resizing) that require additional resources like EC2 Instances, EBS Volumes, and other resources were impaired in the ME-CENTRAL-1 and ME-SOUTH-1 Region. Other AWS Services also experienced error rates and latencies for some workflows. Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure. A detailed summary of the AWS regional incident can be found here: https://health.aws.amazon.com/health/status

What are we doing now

We are actively working to limit the impact on the Neo4j Aura service. However, customers should expect that new deployments in the affected regions may be impaired. Additionally, existing services deployed in these regions may experience reduced availability. Customers with services in these or nearby regions who are concerned about potential operational impact are encouraged to contact Neo4j Customer Support through the usual channels

Please visit AWS Status page for more info:https://health.aws.amazon.com/health/status

Posted Apr 02, 2026 - 06:37 UTC

Resolved

While AWS continues working on this situation, we are closing this incident and invite our customers to monitor the AWS Status on our main Neo4j Status Page under AWS (Amazon Web Services). The latest information from AWS can be found at: https://health.aws.amazon.com/health/status
Posted Mar 06, 2026 - 16:06 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.
The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 06, 2026 - 14:29 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.
The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 06, 2026 - 02:08 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 05, 2026 - 14:39 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 05, 2026 - 02:42 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 04, 2026 - 10:10 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The latest information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Posted Mar 03, 2026 - 22:43 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as soon as more information becomes available.
Posted Mar 03, 2026 - 15:26 UTC

Update

We continue to monitor the situation in the affected AWS Middle East regions.

The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status

We will provide additional updates as soon as more information becomes available.
Posted Mar 03, 2026 - 06:19 UTC

Identified

We are aware of issues in the Middle East regions via our cloud partner AWS, affecting AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain).

The most up-to-date information from AWS is available at: https://health.aws.amazon.com/health/status

We are actively working to limit the impact on the Aura service. However, customers should expect that new deployments in the affected regions may be impaired. Additionally, existing services deployed in these regions may experience reduced availability.

Customers with services in these or nearby regions who are concerned about potential operational impact are encouraged to contact Neo4j Customer Support through the usual channels. Our team is available to advise and assist as needed.
Posted Mar 02, 2026 - 19:55 UTC
This incident affected: AWS (Amazon Web Services) (AWS s3-me-central-1, AWS ec2-me-central-1, AWS eks-me-central-1).