Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Neo4j Aura down?

Neo4j Aura is up

Right now

No. No incidents reported.

Last checked (2026-10-10 07:19 UTC) from status.neo4j.io · every 180s

For agents

proceed

Proceed.

GET upbutler.com/status/neo4j/status.agent.json

MCP: upstream_status {"service":"neo4j"}

Managed graph database.

What Neo4j Aura says

Operational

Taken as is from Neo4j Aura's own status page API. Incident titles and component names below are theirs.

Open status.neo4j.io

What UpButler measured

There is no keyless endpoint of Neo4j Aura that says anything useful, so UpButler does not probe it. To check your own Neo4j Aura account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Neo4j Aura components

80 operational

  • Aura Console (console.neo4j.io)Operational
  • Aura API (api.neo4j.io)Operational
  • Aura AgentOperational
  • Aura MCP ServiceOperational
  • AuraDB Free (*.databases.neo4j.io)Operational
  • Customer Support Portal (support.neo4j.com)Operational

AuraDB Virtual Dedicated Cloud (*.databases.neo4j.io)

  • 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 Professional (*.databases.neo4j.io)

  • AuraDB Professional on AWS (*.databases.neo4j.io)Operational
  • AuraDB Professional on Azure (*.databases.neo4j.io)Operational
  • AuraDB Professional on GCP (*.databases.neo4j.io)Operational

GCP (Google Cloud Platform) Services

  • Google Cloud Platform Google Kubernetes EngineOperational
  • Google Cloud Platform Google Cloud StorageOperational
  • Google Cloud Platform Google Cloud DatastoreOperational
  • Google Cloud Platform Google Cloud NetworkingOperational
  • Google Cloud Platform Google Compute EngineOperational
  • Google Cloud Platform Identity & Access ManagementOperational

AWS (Amazon Web Services)

  • AWS ec2-ap-south-1Operational
  • AWS eks-ap-south-1Operational
  • AWS s3-ap-south-1Operational
  • AWS ec2-ap-southeast-2Operational
  • AWS eks-ap-southeast-2Operational
  • AWS s3-ap-southeast-2Operational
  • AWS s3-ca-central-1Operational
  • AWS ec2-ca-central-1Operational
  • AWS eks-eu-central-1Operational
  • AWS s3-eu-central-1Operational
  • AWS ec2-eu-central-1Operational
  • AWS eks-eu-west-1Operational
  • AWS ec2-eu-west-1Operational
  • AWS s3-eu-west-1Operational
  • AWS s3-eu-west-2Operational
  • AWS eks-eu-west-2Operational
  • AWS ec2-eu-west-2Operational
  • AWS ec2-eu-west-3Operational
  • AWS eks-eu-west-3Operational
  • AWS s3-eu-west-3Operational
  • AWS eks-us-east-1Operational
  • AWS s3-us-east-1Operational
  • AWS eks-us-east-2Operational
  • AWS ec2-us-east-2Operational
  • AWS s3-us-east-2Operational
  • AWS s3-us-west-2Operational
  • AWS eks-us-west-2Operational
  • AWS ec2-us-west-2Operational
  • AWS ec2-ap-northeast-2Operational
  • AWS s3-ap-northeast-2Operational
  • AWS eks-ap-northeast-2Operational
  • AWS eks-ap-southeast-1Operational
  • AWS s3-ap-southeast-1Operational
  • AWS ec2-ap-southeast-1Operational
  • AWS ec2-sa-east-1Operational
  • AWS eks-sa-east-1Operational
  • AWS s3-sa-east-1Operational
  • AWS s3-ap-northeast-1Operational
  • AWS eks-ap-northeast-1Operational
  • AWS ec2-ap-northeast-1Operational
  • AWS ec2-ap-east-1Operational

Component 3rd Party Services

  • User Authentication (Auth0)Operational

Neo4j User Tools

  • 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

AuraDS (*.databases.neo4j.io)

  • AuraDS on AWS (*.databases.neo4j.io)Operational
  • AuraDS on Azure (*.databases.neo4j.io)Operational
  • AuraDS on GCP (*.databases.neo4j.io)Operational

AuraDS Enterprise (*.databases.neo4j.io)

  • AuraDS Enterprise on AWS (*.databases.neo4j.io)Operational
  • AuraDS Enterprise on Azure (*.databases.neo4j.io)Operational
  • AuraDS Enterprise on GCP (*.databases.neo4j.io)Operational

Azure (Microsoft Cloud Computing Services)

  • Azure AKSOperational
  • Azure Private LinkOperational
  • Azure Cloud Services (Compute)Operational
  • Azure Storage ServicesOperational

AuraDB Business Critical (*.databases.neo4j.io)

  • AuraDB Business Critical (*.databases.neo4j.io) on AWSOperational
  • AuraDB Business Critical (*.databases.neo4j.io) on AzureOperational
  • AuraDB Business Critical (*.databases.neo4j.io) on GCPOperational

Aura Graph Analytics

  • Aura Graph Analytics on AWSOperational
  • Aura Graph Analytics on AzureOperational
  • Aura Graph Analytics on GCPOperational

Neo4j Aura incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: no record
  73. 2026-09-23: no record
  74. 2026-09-24: no record
  75. 2026-09-25: no record
  76. 2026-09-26: no record
  77. 2026-09-27: no record
  78. 2026-09-28: no record
  79. 2026-09-29: no record
  80. 2026-09-30: no record
  81. 2026-10-01: no record
  82. 2026-10-02: no record
  83. 2026-10-03: no record
  84. 2026-10-04: no record
  85. 2026-10-05: no record
  86. 2026-10-06: minor incident
  87. 2026-10-07: no incident reported
  88. 2026-10-08: minor incident
  89. 2026-10-09: no incident reported
  90. 2026-10-10: no incident reported
2026-07-132 of 5 days with an incidenttoday

Each bar is a day, coloured by the worst incident Neo4j Aura reported. It is their incident record, not a measurement of uptime.

Incidents
3
0 major or critical
Typical time to resolve
5 h 57 min
median
Nine in ten within
—
90th percentile
Longest
5 h 57 min
record since 2026-10-06
Started (UTC)IncidentImpactLasted
Issue for some customers with instance metrics (endpoint and in Console).minor4 h 13 min
Snapshot Downloads Return Blank Dumpsminor5 h 57 min
AuraDS affected by issues when attempting to restore from snapshotminor5 h 57 min

Get alerted when Neo4j Aura goes down

No account. One email when Neo4j Aura reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Neo4j Aura as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Neo4j Aura's current status in a README or an internal wiki. It updates by itself.

Neo4j Aura status badge

[![Neo4j Aura status](https://upbutler.com/status/neo4j/badge.svg)](https://upbutler.com/status/neo4j)

Tell your outage from Neo4j Aura's

Declare that your project depends on Neo4j Aura. When one of your monitors fails while Neo4j Aura has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - neo4j
Ask before you retry
curl -s https://upbutler.com/status/neo4j/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "neo4j",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Neo4j Aura down right now?
No. As of 2026-10-10 07:19 UTC, Neo4j Aura is up. This page reads the status again every 3 minutes.
How long do Neo4j Aura outages usually last?
Of the 3 incidents Neo4j Aura reported in the last 90 days, half were resolved within 5 h 57 min; the longest took 5 h 57 min. These are the provider's own start and end times.
Where does this status come from?
From Neo4j Aura's own status page API at https://status.neo4j.io. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Neo4j Aura's words.
Can I get an alert when Neo4j Aura goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Neo4j Aura reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/neo4j/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Neo4j Aura status?
Fetch https://upbutler.com/status/neo4j/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"neo4j"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Neo4j Aura's?
Add "neo4j" to the dependencies of your UpButler workspace. When one of your monitors fails while Neo4j Aura has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Neo4j Aura. Status and incident text belong to Neo4j Aura and are read from their public status source; the probe result is UpButler's own measurement.