The Cloud Service Provider is working on the fix deployment and we are continuing to monitor the situation currently.
Posted Oct 29, 2026 - 16:09 UTC
Identified
The Cloud Service Provider has identified the cause and is working on fixing the underlying issue. We will update further on the progress as we receive updates from the CSP.
Posted Oct 29, 2026 - 13:34 UTC
Update
We are continuing to work with the Cloud Service provider to resolve the issue. The regions affected so far are brazilsouth, centralus, canadacentral, northeurope and this list may evolve over time.
Posted Oct 29, 2026 - 11:44 UTC
Update
We are continuing to work with the CSP on the issue. The regions affected so far are brazilsouth, centralus, canadacentral, northeurope and this list may evolve over time.
Posted Oct 29, 2026 - 10:28 UTC
Update
Updating the impact for affected Aura components, based on ongoing investigations.
Posted Oct 29, 2026 - 09:51 UTC
Update
We are continuing to investigate this issue.
Posted Oct 29, 2026 - 09:43 UTC
Update
We are continuing to investigate the issue and are working with the CSP. At this point in time the issue appears to be impacting the AMER regions.
Posted Oct 29, 2026 - 09:36 UTC
Investigating
We are investigating a Cloud Service Provider issue that is impacting some Aura operations in a limited number of regions.
Posted Oct 29, 2026 - 09:06 UTC
This incident affected: Azure (Microsoft Cloud Computing Services) (Azure AKS, Azure Private Link, Azure Cloud Services (Compute), Azure Storage Services), AuraDB Virtual Dedicated Cloud (*.databases.neo4j.io) (AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)), AuraDB Professional (*.databases.neo4j.io) (AuraDB Professional on Azure (*.databases.neo4j.io)), AuraDB Business Critical (*.databases.neo4j.io) (AuraDB Business Critical (*.databases.neo4j.io) on Azure), and Aura API (api.neo4j.io).