Vendor Status Watch

← all vendors

Neo4j Aura status history

Current state: degraded — “Minor Service Outage” per https://status.neo4j.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

4incidents, last 30 days
9incidents, last 90 days
22incidents on record
Incidents per week, last 12 weeks:

How long do Neo4j Aura incidents last?

4.7 hmedian incident duration21 measured
2.1 days90th percentile1 in 10 ran longer
3.6 hmedian, major/critical only6 incidents

From 21 incidents with a vendor-posted start and resolve time. Longest on record: Neo4j Aura Service impacted by Resource Shortage in Azure US East — 15.0 days (2025-11-26 15:47 UTC). Excluded, never estimated: 1 still open / no resolve time. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (22)

StartedIncidentStatusImpactDuration
2026-09-16 08:50 UTCCustomer support portal issuesmonitoringmajoropen
2026-09-09 12:31 UTCConsole and API outageresolvedcritical1 h 08 min
2026-09-03 16:43 UTCA small number of Free Tier instances are experiencing issues updatingresolvednone22 h 52 min
2026-08-20 15:49 UTCAura metrics issue.resolvedminor3 h 21 min
2026-08-05 17:31 UTCPotential unexpected query failures.resolvedminor46 h 03 min
2026-07-23 10:52 UTCIssue impacting Aura instance operationspostmortemmajor29 h 03 min
2026-07-10 17:18 UTCAura Console Impacted - Instance Viewpostmortemminor2 h 05 min
2026-06-30 14:45 UTCAuraDB issue: Errors when running CREATE VECTOR INDEXpostmortemminor2 h 59 min
2026-06-23 11:25 UTCAura console experiencing some intermittent errorspostmortemminor21 h 48 min
2026-05-26 18:23 UTCAura Console Auth errorpostmortemmajor4 h 43 min
2026-03-06 10:18 UTCConsole is not availablepostmortemcritical6 min
2026-03-03 21:35 UTCSubset of MERGE queries lead to setting unexpected property valuespostmortemnone17 h 44 min
2026-03-02 19:55 UTCMiddle East Availability - AWSpostmortemminor3 d 20 h
2026-01-26 19:26 UTCLimited set of queries impacted by Cypher 25 issuepostmortemminor20 h 31 min
2026-01-16 14:25 UTCData science feature on AuraDS , AuraDSE and Aura Professional tiers - Native projection affected.postmortemminor5 h 10 min
2025-11-26 15:47 UTCNeo4j Aura Service impacted by Resource Shortage in Azure US Eastpostmortemmajor14 d 23 h
2025-11-18 15:56 UTCPause / Resume / Destroy operations failingpostmortemminor42 min
2025-10-20 16:43 UTCSeveral operations degraded for AWS instances in region us-east-1postmortemminor4 h 44 min
2025-10-20 09:15 UTCAura operations on AWS affected by an incident in US-EAST-1 regionpostmortemminor1 h 58 min
2025-08-25 13:34 UTCDatabase instance write performance impactedpostmortemminor2 d 3 h
2025-08-22 11:02 UTCCMI & Instance Operations Unavailablepostmortemmajor2 h 29 min
2025-08-19 09:19 UTCSome issues with backupspostmortemminor2 h 44 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Neo4j Aura with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "neo4j-aura"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}