Provider
Neo4j AuraIncident detail
Middle East Availability - AWS
Timeline window
to
Outage alerts
Get alerted the next time Neo4j Aura breaks
Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
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.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
Identified
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.
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
Resolved
## 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