- Detected by Pingoru
- Oct 13, 2026, 09:15 AM UTC
- Resolved
- Oct 13, 2026, 12:08 PM UTC
- Duration
- 2h 52m
Affected: Aura Console (console.neo4j.io)Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline · 4 updates
-
investigating Oct 13, 2026, 09:15 AM UTC
We are investigating an issue impacting metrics in the Aura Console and via the metric endpoint.
-
identified Oct 13, 2026, 10:13 AM UTC
We have identified that a Cloud Service Provider related issue is impacting the current issue. We have opened a support case with the Cloud Service Provider and will update further once we have more detail.
-
monitoring Oct 13, 2026, 11:01 AM UTC
We believe that the Cloud Service Provider issue has been resolved, as we are no longer seeing issues from our internal systems. We will continue to monitor the situation, while we wait for confirmation from the Cloud Service provider.
-
resolved Oct 13, 2026, 12:08 PM UTC
We have had confirmation from the Cloud Service Provider that the issue has now been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2026, 02:58 PM UTC
- Resolved
- Oct 08, 2026, 07:11 PM UTC
- Duration
- 4h 13m
Affected: Aura Console (console.neo4j.io)Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline · 6 updates
-
investigating Oct 08, 2026, 02:58 PM UTC
We are investigating an issue with metrics in the Aura Console and via the metric endpoint.
-
identified Oct 08, 2026, 03:36 PM UTC
We continue to investigate the root cause. The issue is limited to customers on us-central1 on GCP Aura instances are running and no operation is affected.
-
identified Oct 08, 2026, 04:30 PM UTC
We are working with the cloud service provider to investigate the nature of the issue. Our checks confirm that only a subset of customers running in the us-central1 regions are affected.
-
identified Oct 08, 2026, 05:30 PM UTC
We continue to work with the cloud service provider to get a solution.
-
identified Oct 08, 2026, 06:41 PM UTC
We continue to work with the cloud service provider to get a solution.
-
resolved Oct 08, 2026, 07:11 PM UTC
This incident has now been resolved, metrics should now operate as normal.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 09:22 AM UTC
- Resolved
- Oct 06, 2026, 03:19 PM UTC
- Duration
- 5h 56m
Affected: AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on Azure
Timeline · 5 updates
-
investigating Oct 06, 2026, 09:22 AM UTC
We are investigating an issue where, despite backups completing successfully, snapshot downloads are returning blank dumps. Restoring from a snapshot through the Aura console or API is not believed to be affected, and we are verifying this now. We will share an update as soon as we have more information.
-
investigating Oct 06, 2026, 10:43 AM UTC
We are continuing to investigate the issue. Restore operations are not affected as part of this issue.
-
investigating Oct 06, 2026, 01:41 PM UTC
We are continuing to investigate this issue.
-
investigating Oct 06, 2026, 01:41 PM UTC
We are continuing to investigate the issue.
-
resolved Oct 06, 2026, 03:19 PM UTC
A fix has been deployed; snapshot downloads now contain the appropriate data.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 08:07 AM UTC
- Resolved
- Oct 06, 2026, 02:04 PM UTC
- Duration
- 5h 56m
Affected: AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)
Timeline · 6 updates
-
identified Oct 06, 2026, 08:07 AM UTC
We have identified an issue when attempting to restore from snapshots on AuraDS. We have a fix ready and will deploy this soon. In the meantime you can restore from a backup instead.
-
identified Oct 06, 2026, 09:07 AM UTC
We have clearly identified the root cause and continue to work on a fix for this issue.
-
identified Oct 06, 2026, 10:03 AM UTC
We continue to work on a fix for this issue.
-
identified Oct 06, 2026, 12:14 PM UTC
A fix is being deployed and will roll out to affected customers shortly.
-
monitoring Oct 06, 2026, 01:35 PM UTC
The fix is rolling out and affected customers should see the functionality restored progressively.
-
resolved Oct 06, 2026, 02:04 PM UTC
We have deployed the fix to all customers.
Read the full incident report →
- Detected by Pingoru
- Sep 17, 2026, 04:46 PM UTC
- Resolved
- Sep 17, 2026, 07:55 PM UTC
- Duration
- 3h 8m
Affected: AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAura Graph Analytics on Azure
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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.
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2026, 08:50 AM UTC
- Resolved
- Sep 16, 2026, 02:31 PM UTC
- Duration
- 5h 40m
Affected: Customer Support Portal (support.neo4j.com)
Timeline · 6 updates
-
identified Sep 16, 2026, 08:50 AM UTC
Our service provider for the support portal is experiencing some outage - See https://status.salesforce.com/products/Salesforce_Services If you experience issues submitting a new support case, please send email to [email protected]
-
identified Sep 16, 2026, 09:16 AM UTC
Our support portal provider is still working on addressing the issue. See details here https://status.salesforce.com/incidents/20004433
-
identified Sep 16, 2026, 10:11 AM UTC
Our support portal provider continues to work on addressing the issue. See details here https://status.salesforce.com/incidents/20004433
-
monitoring Sep 16, 2026, 11:30 AM UTC
A fix is being rolled out and the portal should become less impacted by errors over time. See details https://status.salesforce.com/incidents/20004433
-
monitoring Sep 16, 2026, 12:29 PM UTC
Our support portal provider continues to roll out a fix.
-
resolved Sep 16, 2026, 02:31 PM UTC
A fix has been deployed and all functionality should now be recovered.
Read the full incident report →
Critical September 9, 2026 - Detected by Pingoru
- Sep 09, 2026, 12:31 PM UTC
- Resolved
- Sep 09, 2026, 01:39 PM UTC
- Duration
- 1h 8m
Affected: Aura Console (console.neo4j.io)Aura Graph Analytics on AWSAura Graph Analytics on AzureAura Graph Analytics on GCPAura API (api.neo4j.io)Aura AgentAura MCP Service
Timeline · 6 updates
-
investigating Sep 09, 2026, 12:31 PM UTC
We are currently investigating an issue affecting the Aura console console.neo4j.io and the API api.neo4j.io
-
identified Sep 09, 2026, 12:54 PM UTC
We have identified the source of the issue and are currently working on a solution.
-
identified Sep 09, 2026, 01:10 PM UTC
We continue to work on addressing the issue.
-
identified Sep 09, 2026, 01:26 PM UTC
We have made good progress and are recovering the problematic component.
-
monitoring Sep 09, 2026, 01:36 PM UTC
We have deployed a fix and the affected services are recovering.
-
resolved Sep 09, 2026, 01:39 PM UTC
All affected components are now fully recovered.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 04:43 PM UTC
- Resolved
- Sep 04, 2026, 03:36 PM UTC
- Duration
- 22h 52m
Affected: AuraDB Free (*.databases.neo4j.io)
Timeline · 3 updates
-
investigating Sep 03, 2026, 04:43 PM UTC
We are currently investigating this issue.
-
identified Sep 04, 2026, 10:23 AM UTC
The issue has been identified, instances remain available and steps to resolve for the instances impacted being reviewed currently.
-
resolved Sep 04, 2026, 03:36 PM UTC
All instances are available, manual steps to unblock the remaining small number of instances was undertaken to resolve.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 03:49 PM UTC
- Resolved
- Aug 20, 2026, 07:10 PM UTC
- Duration
- 3h 21m
Affected: Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2026, 05:31 PM UTC
- Resolved
- Aug 07, 2026, 03:34 PM UTC
- Duration
- 1d 22h
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCPAuraDB Free (*.databases.neo4j.io)
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 05:01 PM UTC
- Resolved
- Jul 24, 2026, 03:56 PM UTC
- Duration
- 22h 55m
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCPAura API (api.neo4j.io)AuraDB Free (*.databases.neo4j.io)
Timeline · 29 updates
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 05:41 PM UTC
- Resolved
- Jul 10, 2026, 05:53 PM UTC
- Duration
- 11m
Affected: Aura Console (console.neo4j.io)
Timeline · 2 updates
-
monitoring Jul 10, 2026, 05:41 PM UTC
The third-party service that Aura depends on has restored normal operations and the Neo4j Aura systems have recovered. Our team is actively monitoring the issue to confirm Aura Console is performing as expected.
-
monitoring Jul 10, 2026, 05:42 PM UTC
The third-party service that Aura depends on has restored normal operations and the Neo4j Aura systems have recovered. Our team is actively monitoring the issue to confirm Aura Console is performing as expected.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 05:18 PM UTC
- Resolved
- Jul 10, 2026, 07:23 PM UTC
- Duration
- 2h 5m
Affected: Aura Console (console.neo4j.io)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 02:45 PM UTC
- Resolved
- Jun 30, 2026, 05:45 PM UTC
- Duration
- 2h 59m
Affected: AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCP
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 11:25 AM UTC
- Resolved
- Jun 24, 2026, 09:14 AM UTC
- Duration
- 21h 48m
Affected: Aura Console (console.neo4j.io)Aura API (api.neo4j.io)
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 06:23 PM UTC
- Resolved
- May 26, 2026, 11:06 PM UTC
- Duration
- 4h 43m
Affected: Aura Console (console.neo4j.io)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 10:18 AM UTC
- Resolved
- Mar 06, 2026, 10:25 AM UTC
- Duration
- 6m
Affected: Aura Console (console.neo4j.io)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 09:35 PM UTC
- Resolved
- Mar 04, 2026, 03:19 PM UTC
- Duration
- 17h 44m
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCPAuraDB Free (*.databases.neo4j.io)
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 07:55 PM UTC
- Resolved
- Mar 06, 2026, 04:06 PM UTC
- Duration
- 3d 20h
Affected: AWS s3-me-central-1AWS ec2-me-central-1AWS eks-me-central-1
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 07:26 PM UTC
- Resolved
- Jan 27, 2026, 03:58 PM UTC
- Duration
- 20h 31m
Affected: AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Free (*.databases.neo4j.io)
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 02:25 PM UTC
- Resolved
- Jan 16, 2026, 07:36 PM UTC
- Duration
- 5h 10m
Affected: AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 03:47 PM UTC
- Resolved
- Dec 11, 2025, 03:39 PM UTC
- Duration
- 14d 23h
Affected: AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on Azure
Timeline · 20 updates
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 03:56 PM UTC
- Resolved
- Nov 18, 2025, 04:39 PM UTC
- Duration
- 42m
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)AuraDB Professional on Azure (*.databases.neo4j.io)AuraDS Enterprise on Azure (*.databases.neo4j.io)AuraDS on Azure (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)AuraDB Professional on GCP (*.databases.neo4j.io)AuraDS Enterprise on GCP (*.databases.neo4j.io)AuraDS on GCP (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on GCPAura API (api.neo4j.io)AuraDB Free (*.databases.neo4j.io)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 04:43 PM UTC
- Resolved
- Oct 20, 2025, 09:28 PM UTC
- Duration
- 4h 44m
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAura Graph Analytics on AWS
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:15 AM UTC
- Resolved
- Oct 20, 2025, 11:13 AM UTC
- Duration
- 1h 58m
Affected: AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)AuraDB Professional on AWS (*.databases.neo4j.io)AuraDS on AWS (*.databases.neo4j.io)AuraDS Enterprise on AWS (*.databases.neo4j.io)AuraDB Business Critical (*.databases.neo4j.io) on AWSAura Graph Analytics on AWS
Timeline · 6 updates
Read the full incident report →