Neo4j Aura Service impacted by Resource Shortage in Azure US East

Incident Report for Neo4j Aura

Postmortem

What Happened

Starting at 13:26 UTC on November 24th Microsoft Azure region eastus experienced a stock out situation, which impacted operations for all tiers of Neo4j Aura in that specific region. Additional capacity was requested straight away, but not until 17:06 UTC on December 10th did enough additional resources become available to resume all normal operations.

How the service was affected

All tiers within the Neo4j Aura Service were impacted when performing the following operations during this incident: Create, Resize (CPU and Storage), Clone, Pause and Resume. If Microsoft Azure resources were unavailable when requesting these types of Neo4j operations, the operation would fail, and the Neo4j instance would become unavailable until Azure was able to provision additional resources.

What are we doing now

To mitigate the scope of impact of future regional stock out issues, Neo4j is implementing the following measures:

Closely monitoring resource capacity to improve stockout predictions.
Regular calls with with our Cloud Service Provider to:
- Learn about where regional resource capacity restrictions are forecast.
- Plan for more resources in restricted regions.
Investigating other deployment models to allow us to keep Aura running in situations where 3 Availability Zones are not available.

Posted Feb 04, 2026 - 15:18 UTC

Resolved

Cloud resources have become available in USEAST2 and no further customer impact has been detected.
This incident is resolved.

Posted Dec 11, 2025 - 15:39 UTC

Monitoring

Cloud resources have become available in USEAST2 and we will monitor for a few hours to ensure there is no further customer impact.

Posted Dec 11, 2025 - 10:24 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region.

We are working with our cloud partner and will resume updates once we have an ETA to share.

Posted Dec 05, 2025 - 16:59 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, affecting the following operations: Create, Resize (CPU and Storage), Pause, Resume.

If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources.

Posted Dec 05, 2025 - 10:20 UTC

Update

Posted Dec 04, 2025 - 09:52 UTC

Update

Posted Dec 03, 2025 - 10:52 UTC

Update

Posted Dec 02, 2025 - 10:03 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume.

If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance may become unavailable or degraded until Azure is able to provision additional resources.

Posted Dec 01, 2025 - 09:54 UTC

Update

We continue to work with Microsoft Azure. No expected improvements in addressing the issues around cloud resources in the affected regions before next week.

Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

We will resume updates after this weekend or earlier if we have more information.

Posted Nov 28, 2025 - 16:23 UTC

Update

We continue to work with our cloud infrastructure provider.
Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

Posted Nov 28, 2025 - 10:55 UTC

Update

We continue to work with our cloud infrastructure provider.
Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

Posted Nov 28, 2025 - 08:54 UTC

Update

We continue to work with our cloud infrastructure provider.
Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

Posted Nov 28, 2025 - 04:54 UTC

Update

We continue to work with our cloud infrastructure provider . Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

Posted Nov 28, 2025 - 00:09 UTC

Update

We continue to work with our cloud infrastructure provider. Aura operations affected: Create, Resize (CPU and Storage), Pause, Clone, Resume.

Posted Nov 27, 2025 - 20:11 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Clone, Resume.

As Azure resources become available when performing some Aura operations, the impacted instances may progressively recover and operations successfully complete.

We continue to monitor progress, work with Microsoft Azure Infrastructure issues and will update.

Posted Nov 27, 2025 - 17:07 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume.

If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance will become unavailable until Azure is able to provision additional resources.

Posted Nov 27, 2025 - 14:33 UTC

Update

The Neo4j Aura Service continues to be impacted by Azure Infrastructure issues in the US east region, effecting the following operations: Create, Resize (CPU and Storage), Pause, Resume.

If Azure resources are unavailable when requesting these types of Neo4j Aura operations, they will fail and the Neo4j Aura instance will become unavailable until Azure is able to provision additional resources.

Posted Nov 27, 2025 - 10:52 UTC

Update

Neo4j continues working with Microsoft via an Azure cloud ticket and is awaiting updates on their resolution of the Azure Infrastructure issues. Some resources have been made available, and impacted Neo4j Services have resumed operation. Customers have been notified.

The Neo4j Aura Service is impacted when performing the following operations: Create, Resize (CPU and Storage), Pause, Resume. If Azure resources are unavailable when requesting these types of Neo4j operations, the operation will fail, and the Neo4j instance will become unavailable until Azure is able to provision additional resources.

Posted Nov 26, 2025 - 20:33 UTC

Identified

Neo4j opened a ticket with Azure and is awaiting updates on their resolution of the Azure Infrastructure issues.
Impact on Neo4j Aura Services: Create, Resize (CPU and Storage), Pause, Resume.

Posted Nov 26, 2025 - 15:47 UTC

This incident affected: 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)), AuraDS (*.databases.neo4j.io) (AuraDS on Azure (*.databases.neo4j.io)), and AuraDB Business Critical (*.databases.neo4j.io) (AuraDB Business Critical (*.databases.neo4j.io) on Azure).