Issue impacting certain database operations for Aura customers on Azure

Update timeline

1. investigating Sep 17, 2026, 04:46 PM UTC

   We are currently aware of an issue that is impacting certain database operations, such as create, delete, clone for customers using Aura on Azure.

2. identified Sep 17, 2026, 05:11 PM UTC

   We have identified the issue and are working towards a solution. At this time, certain database operations, such as create, delete, and clone for customers using Neo4j Aura on Azure only, continue to be impacted.

3. monitoring Sep 17, 2026, 07:06 PM UTC

   A fix has been deployed to all affected environments. We will monitor the situation to ensure that the fix fully resolves the issue.

4. resolved Sep 17, 2026, 07:55 PM UTC

   After deploying the fix, we monitored the impacted instances, operational metrics, and errors. This incident is now resolved.

5. postmortem Oct 16, 2026, 04:23 PM UTC

   # What happened On Thursday, 17 September 2026 at 13:52 UTC, a deployment-time conflict between concurrent operations caused a credential used by a core Aura component to authenticate with Azure-hosted infrastructure to be removed. As existing authentication tokens expired, the component began returning errors for some Aura instances hosted on Azure, affecting certain database operations. We traced the errors to the missing credential, created a new one, stored it securely, and performed a rolling deployment of the affected component, which completed at 18:39 UTC. A small number of database creation requests that were in progress during the outage were left in an incomplete state and needed manual remediation. This was completed at 19:48 UTC, and the incident was marked resolved at 19:55 UTC. # How the service was affected The impact was limited to Aura instances hosted on Azure. Other cloud providers were not affected. * **Database operations:** Customers were unable to perform certain database operations, such as create, delete, and clone, on some Azure instances during the incident window. A small number of creates that were in progress became stuck and were recovered manually. * **Management visibility:** Some Azure-hosted instances were temporarily not visible or manageable in Aura Console. * **Metrics gaps:** Metrics endpoints for some Azure instances returned intermittent errors, leaving short gaps in metrics data for the affected period. This data will not be backfilled. Azure instances that were already running remained available and continued to serve workloads normally. # What we are doing now We are taking the following steps to help prevent a recurrence and improve our response: * **Earlier detection and communication:** We will improve monitoring and alerting, and evaluate automated credential checks, so issues are detected and customers are informed sooner. * **Recovery from incomplete database creation:** We will fix a defect that can leave a database creation stuck if an infrastructure call fails partway through, so the system recovers on its own. * **Authentication review:** We will review how this component authenticates with cloud providers, to remove single points of failure and reduce the risk of this type of conflict recurring.