All Systems Operational

About This Site

Welcome to the Neo4j status page!
Having trouble please get in touch at https://support.neo4j.com or send us a mail at support@neo4j.com.

Aura Console (console.neo4j.io) ? Operational
AuraDB Enterprise (*.databases.neo4j.io) ? Operational
AuraDB Enterprise on AWS (*.databases.neo4j.io) ? Operational
AuraDB Enterprise on Azure (*.databases.neo4j.io) ? Operational
AuraDB Enterprise on GCP (*.databases.neo4j.io) ? Operational
AuraDB Professional (*.databases.neo4j.io) ? Operational
AuraDB Professional on AWS (*.databases.neo4j.io) ? Operational
AuraDB Professional on Azure (*.databases.neo4j.io) ? Operational
AuraDB Professional on GCP (*.databases.neo4j.io) ? Operational
AuraDS Enterprise (*.databases.neo4j.io) ? Operational
AuraDS Enterprise on AWS (*.databases.neo4j.io) ? Operational
AuraDS Enterprise on Azure (*.databases.neo4j.io) ? Operational
AuraDS Enterprise on GCP (*.databases.neo4j.io) ? Operational
AuraDS (*.databases.neo4j.io) ? Operational
AuraDS on AWS (*.databases.neo4j.io) ? Operational
AuraDS on Azure (*.databases.neo4j.io) ? Operational
AuraDS on GCP (*.databases.neo4j.io) ? Operational
Aura API (api.neo4j.io) Operational
AuraDB Free (*.databases.neo4j.io) ? Operational
Neo4j User Tools Operational
Bloom (bloom.neo4j.io) ? Operational
Browser (browser.neo4j.io) ? Operational
Data Importer (data-importer.neo4j.io) ? Operational
AWS (Amazon Web Services) ? Operational
AWS ec2-ap-south-1 Operational
AWS eks-ap-south-1 Operational
AWS s3-ap-south-1 Operational
AWS ec2-ap-southeast-2 Operational
AWS eks-ap-southeast-2 Operational
AWS s3-ap-southeast-2 Operational
AWS s3-ca-central-1 Operational
AWS ec2-ca-central-1 Operational
AWS eks-eu-central-1 Operational
AWS s3-eu-central-1 Operational
AWS ec2-eu-central-1 Operational
AWS eks-eu-west-1 Operational
AWS ec2-eu-west-1 Operational
AWS s3-eu-west-1 Operational
AWS s3-eu-west-2 Operational
AWS eks-eu-west-2 Operational
AWS ec2-eu-west-2 Operational
AWS ec2-eu-west-3 Operational
AWS eks-eu-west-3 Operational
AWS s3-eu-west-3 Operational
AWS eks-us-east-1 Operational
AWS s3-us-east-1 Operational
AWS eks-us-east-2 Operational
AWS ec2-us-east-2 Operational
AWS s3-us-east-2 Operational
AWS s3-us-west-2 Operational
AWS eks-us-west-2 Operational
AWS ec2-us-west-2 Operational
AWS ec2-ap-northeast-2 Operational
AWS s3-ap-northeast-2 Operational
AWS eks-ap-northeast-2 Operational
AWS eks-ap-southeast-1 Operational
AWS s3-ap-southeast-1 Operational
AWS ec2-ap-southeast-1 Operational
AWS eks-eu-north-1 Operational
AWS s3-eu-north-1 Operational
AWS ec2-eu-north-1 Operational
AWS ec2-sa-east-1 Operational
AWS eks-sa-east-1 Operational
AWS s3-sa-east-1 Operational
Azure (Microsoft Cloud Computing Services) Operational
Azure AKS Operational
Azure Private Link Operational
Azure Cloud Services (Compute) Operational
Azure Storage Services Operational
GCP (Google Cloud Platform) Services ? Operational
Google Cloud Platform Google Kubernetes Engine Operational
Google Cloud Platform Google Cloud Storage Operational
Google Cloud Platform Google Cloud Datastore Operational
Google Cloud Platform Google Cloud Networking Operational
Google Cloud Platform Google Compute Engine Operational
Google Cloud Platform Identity & Access Management Operational
Component 3rd Party Services Operational
User Authentication (Auth0) ? Operational
Customer Support Portal (support.neo4j.com) ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jun 13, 2024

No incidents reported today.

Jun 12, 2024

No incidents reported.

Jun 11, 2024

No incidents reported.

Jun 10, 2024

No incidents reported.

Jun 9, 2024

No incidents reported.

Jun 8, 2024

No incidents reported.

Jun 7, 2024

No incidents reported.

Jun 6, 2024

No incidents reported.

Jun 5, 2024

No incidents reported.

Jun 4, 2024
Resolved - We have now completed the roll out of the 5.20 versions to all tiers of Aura and this now address the issues with cloning.
Jun 4, 09:57 UTC
Update - We have further narrowed down the root cause and can confirm that cloning from some existing AuraDB instances to other AuraDB or AuraDS instances is impacted.
A small subset of customers using AuraDB may be affected. This effects ONLY existing AuraDB instances that are running version 5.20. To determine if you are impacted, use cypher to check your Neo4j version (see example).

- call dbms.components() yield name, versions, edition unwind versions as version return name, version, edition;
- Neo4j Kernel 5.20-aura enterprise

We are working on a fix, which is to roll out 5.20. We will update this incident with an updated status on Monday, June 3rd.

May 31, 21:15 UTC
Identified - We have identified the root cause and can confirm that only cloning to AuraDS is impacted.
A small subset of customers using AuraDS may be affected.
We are working on a fix.

May 31, 11:39 UTC
Update - We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure.
We will keep you updated as we determine the cause of the issue and work toward a resolution.

May 31, 07:02 UTC
Update - We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure.
We will keep you updated as we determine the cause of the issue and work toward a resolution.

May 31, 04:05 UTC
Investigating - We are currently investigating an issue where customers doing a clone operation from AuraDB to AuraDS will see a failure. We will keep you updated as we determine the cause of the issue and work toward a resolution.
May 30, 23:07 UTC
Resolved - We have successfully rolled out a fix and this issue is now fixed.
Jun 4, 09:56 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 4, 07:00 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 4, 01:08 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 3, 13:19 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 3, 07:02 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 3, 01:00 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 2, 19:00 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

The root cause has been identified, and we are working on rolling out a fix.

Jun 2, 13:28 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

We have identified the root cause and are working on rolling out a fix.

Jun 2, 07:02 UTC
Update - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve database user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

We have identified the root cause and are working on rolling out a fix.

Jun 2, 01:00 UTC
Identified - We have identified a problem with the routing of some internal messages, which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. For example, such commands and queries might involve user management.

The workaround is to directly connect to the system database and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system".
If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

We have identified the root cause and are working on rolling out a fix.

Jun 1, 17:36 UTC
Update - We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves using the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify "system" as the database name to connect to in the driver's code.

We are currently investigating the root cause and will update this incident with progress.

Jun 1, 10:17 UTC
Update - We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves updating the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify system as the database name to connect to.

We are currently investigating the root cause and will update this incident with progress.

Jun 1, 04:04 UTC
Investigating - We have identified a problem with the routing of some internal messages which impacts some operations for Aura Enterprise and Aura Professional customers.

The scope of operations would be anything that involves updating the system database while connected to the neo4j database. Such commands and queries might involve user management as an example.

The workaround is to connect to the system database directly and run these commands. If using Workspace or Browser, you can switch to the system database with the command ":USE system". If using the Neo4j drivers, specify system as the database name to connect to.

We are currently investigating the root cause and will update this incident with progress.

May 31, 22:03 UTC
Jun 3, 2024
Jun 2, 2024
Jun 1, 2024
May 31, 2024
May 30, 2024