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 Virtual Dedicated Cloud (*.databases.neo4j.io)
Operational
AuraDB Virtual Dedicated Cloud on AWS (*.databases.neo4j.io)
Operational
AuraDB Virtual Dedicated Cloud on Azure (*.databases.neo4j.io)
Operational
AuraDB Virtual Dedicated Cloud on GCP (*.databases.neo4j.io)
Operational
AuraDB Business Critical (*.databases.neo4j.io)
Operational
AuraDB Business Critical (*.databases.neo4j.io) on AWS
Operational
AuraDB Business Critical (*.databases.neo4j.io) on Azure
Operational
AuraDB Business Critical (*.databases.neo4j.io) on GCP
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
Aura Graph Analytics
Operational
Aura Graph Analytics on AWS
Operational
Aura Graph Analytics on Azure
Operational
Aura Graph Analytics on GCP
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
Aura Agent
Operational
Aura MCP Service
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
Aura Customer Metrics (customer-metrics-api.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 ec2-sa-east-1
Operational
AWS eks-sa-east-1
Operational
AWS s3-sa-east-1
Operational
AWS s3-ap-northeast-1
Operational
AWS eks-ap-northeast-1
Operational
AWS ec2-ap-northeast-1
Operational
AWS ec2-ap-east-1
Operational
AWS eks-ap-east-1
Operational
AWS s3-ap-east-1
Operational
AWS eks-eu-north-1
Operational
AWS ec2-eu-north-1
Operational
AWS s3-eu-north-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
Scheduled Maintenance
TLS certificate chain update (SSL.com root migration) Nov 10, 2026 08:00-20:00 UTC
Planned start - 08:00 UTC, 11 November 2026
We are updating the main certificate for neo4j.io.
No action is required if you connect to Aura using standard, up-to-date TLS clients (supported Neo4j drivers with default trust, current browsers).
You could be impacted by this change if you hardcode or pin SSL.com intermediate or root certificates when connecting to Aura endpoints on neo4j.io.
What is changing:
- The public certificate chain presented on affected neo4j.io endpoints, including database connectivity.
- The trust path your clients use when validating those endpoints.
You may need to update your environment only if you:
- Pin SSL.com intermediate or root certificates, or a fixed leaf public key, when connecting to *.neo4j.io Aura endpoints (including database URLs)
- Use a custom trust store that does not include SSL.com TLS RSA Root CA 2022 or that only trusts the legacy SSL.com / cross-sign chain.
CAUTION: Neo4j discourage pinning intermediate CAs for Aura. Use default system trust and keep Neo4j drivers and browsers up to date.
Further information
SSL.com is migrating public TLS issuance from legacy 2016 trust hierarchies to newer 2022 roots. We will deploy an updated leaf certificate and chain that validates through SSL.com TLS Issuing RSA CA R1 to SSL.com TLS RSA Root CA 2022, replacing the previous chain (legacy SSL.com RSA subCA, 2016-era root, and cross-signed intermediates).
These PKI changes originate with SSL.com (our public CA), not with a separate Neo4j-operated CA for Aura. We are updating the deployed material so TLS remains trusted on current operating systems and browsers and aligns with modern root-program requirements.
Posted on Nov 06, 2026 - 17:19 UTC
We are updating the main certificate for neo4j.io.
No action is required if you connect to Aura using standard, up-to-date TLS clients (supported Neo4j drivers with default trust, current browsers).
You could be impacted by this change if you hardcode or pin SSL.com intermediate or root certificates when connecting to Aura endpoints on neo4j.io.
What is changing:
- The public certificate chain presented on affected neo4j.io endpoints, including database connectivity.
- The trust path your clients use when validating those endpoints.
You may need to update your environment only if you:
- Pin SSL.com intermediate or root certificates, or a fixed leaf public key, when connecting to *.neo4j.io Aura endpoints (including database URLs)
- Use a custom trust store that does not include SSL.com TLS RSA Root CA 2022 or that only trusts the legacy SSL.com / cross-sign chain.
CAUTION: Neo4j discourage pinning intermediate CAs for Aura. Use default system trust and keep Neo4j drivers and browsers up to date.
Further information
SSL.com is migrating public TLS issuance from legacy 2016 trust hierarchies to newer 2022 roots. We will deploy an updated leaf certificate and chain that validates through SSL.com TLS Issuing RSA CA R1 to SSL.com TLS RSA Root CA 2022, replacing the previous chain (legacy SSL.com RSA subCA, 2016-era root, and cross-signed intermediates).
These PKI changes originate with SSL.com (our public CA), not with a separate Neo4j-operated CA for Aura. We are updating the deployed material so TLS remains trusted on current operating systems and browsers and aligns with modern root-program requirements.
Posted on Nov 06, 2026 - 17:19 UTC