- 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 · 6 updates
-
identified Jan 26, 2026, 07:26 PM UTC
We have identified an issue that may affect a limited set of Cypher 25 queries for AuraDB Free, Professional and AuraDS. This may affect: - Queries using the conditional query WHEN in combination with a non-grouping aggregation over null values result in an incorrect number of rows returned. - Queries using NEXT can produce an unexpected variable not defined error in some instances. We are actively working on a fix and will update this page as more information becomes available.
-
identified Jan 27, 2026, 01:37 AM UTC
We have identified a solution for this issue and will be rolling out in Aura. Once the update has been deployed we will update this tatus page.
-
identified Jan 27, 2026, 09:50 AM UTC
We are rolling out the fix and will update you when this is completed.
-
monitoring Jan 27, 2026, 11:10 AM UTC
The fix has rolled out to the affected components, we are now monitoring the situation at this time.
-
monitoring Jan 27, 2026, 02:51 PM UTC
We are continuing to monitor the situation at this time.
-
resolved Jan 27, 2026, 03:58 PM UTC
The fix has been fully deployed to all impacted instances. This incident is now resolved.
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 →
- Detected by Pingoru
- Aug 26, 2025, 05:17 PM UTC
- Resolved
- Aug 27, 2025, 04:46 PM UTC
- Duration
- 23h 28m
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 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 AzureAura Graph Analytics 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 Graph Analytics on GCPAuraDB Free (*.databases.neo4j.io)
Timeline · 16 updates
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 11:02 AM UTC
- Resolved
- Aug 22, 2025, 01:31 PM UTC
- Duration
- 2h 29m
Affected: Aura Console (console.neo4j.io)Data Importer (data-importer.neo4j.io)Aura Customer Metrics (customer-metrics-api.neo4j.io)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 09:19 AM UTC
- Resolved
- Aug 19, 2025, 12:04 PM UTC
- Duration
- 2h 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 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 AzureAura Graph Analytics 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 Graph Analytics on GCP
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2025, 08:40 PM UTC
- Resolved
- Jul 03, 2025, 06:32 PM UTC
- Duration
- 2d 21h
Affected: AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Business Critical (*.databases.neo4j.io) on GCP
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 09:48 AM UTC
- Resolved
- Jun 27, 2025, 10:36 AM UTC
- Duration
- 48m
Affected: AuraDB Business Critical (*.databases.neo4j.io) on AWSAuraDB Business Critical (*.databases.neo4j.io) on AzureAuraDB Business Critical (*.databases.neo4j.io) on GCP
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:42 PM UTC
- Resolved
- Jun 13, 2025, 05:18 AM UTC
- Duration
- 10h 35m
Affected: Aura Console (console.neo4j.io)
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 04:41 AM UTC
- Resolved
- Jun 10, 2025, 09:46 AM UTC
- Duration
- 5h 4m
Affected: Aura Console (console.neo4j.io)AuraDB Free (*.databases.neo4j.io)
Timeline · 4 updates
-
investigating Jun 10, 2025, 04:41 AM UTC
Some Free-tier users are experiencing issues connecting to their instances through the default console experience. As a temporary workaround, we recommend switching to the classic console experience by going to your profile → Experience → Classic experience. Our team is actively investigating the issue and working toward a resolution
-
investigating Jun 10, 2025, 06:13 AM UTC
Some Free-tier users are experiencing issues connecting to their instances through the default console experience. As a temporary workaround, we recommend switching to the classic console experience by going to your profile → Experience → Classic experience. Our team is actively investigating the issue and working toward a resolution
-
identified Jun 10, 2025, 08:12 AM UTC
We’ve identified the potential cause of the issue and are currently working on mitigating it. We’ll keep you updated as soon as we have more information to share.
-
resolved Jun 10, 2025, 09:46 AM UTC
This issue is resolved after rolling out a fix in production. Users can now connect to the free tier instances from the new console without any issues.
Read the full incident report →
- Detected by Pingoru
- May 21, 2025, 06:51 PM UTC
- Resolved
- May 22, 2025, 09:09 AM UTC
- Duration
- 14h 17m
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 · 15 updates
Read the full incident report →