We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Mar 04, 2026 - 10:10 UTC
Update - We continue to monitor the situation in the affected AWS Middle East regions.
We will provide additional updates as more information becomes available. Please review the AWS recommendation on the website above.
Mar 03, 2026 - 22:43 UTC
Update - We continue to monitor the situation in the affected AWS Middle East regions.
We will provide additional updates as soon as more information becomes available.
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).
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.
Mar 02, 2026 - 19:55 UTC
Resolved -
The fix has been fully deployed to all impacted instances. This incident is now resolved.
Mar 4, 15:19 UTC
Monitoring -
The fix has now been deployed to those instances impacted and we are monitoring the situation.
Mar 4, 14:07 UTC
Update -
The fix is being deployed and the status page will be updated upon completion of the full deployment
Mar 4, 04:52 UTC
Update -
The fix is being deployed and the status page will be updated upon completion of the full deployment of the fix.
Mar 4, 01:39 UTC
Identified -
A recent update resulted in MERGE queries which referenced the same merged property on both the left and right hand side of an ON MATCH SET or ON CREATE SET clause deleting that property from the node, or setting it to an invalid value during query runtime. The node being matched against must have had at least one property uniqueness constraint present.
A fix has been identified and will be applied as soon as possible. Instances marked as "Production" are not impacted.
Mar 3, 21:35 UTC