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
Mar 6, 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.
Mar 6, 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.
Mar 6, 02:08 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 3, 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 2, 19:55 UTC