Neo4j Aura status history
Current state: degraded — “Minor Service Outage” per https://status.neo4j.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Neo4j Aura incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 08:50 UTC | Customer support portal issues | monitoring | major | open |
| 2026-09-09 12:31 UTC | Console and API outage | resolved | critical | 1 h 08 min |
| 2026-09-03 16:43 UTC | A small number of Free Tier instances are experiencing issues updating | resolved | none | 22 h 52 min |
| 2026-08-20 15:49 UTC | Aura metrics issue. | resolved | minor | 3 h 21 min |
| 2026-08-05 17:31 UTC | Potential unexpected query failures. | resolved | minor | 46 h 03 min |
| 2026-07-23 10:52 UTC | Issue impacting Aura instance operations | postmortem | major | 29 h 03 min |
| 2026-07-10 17:18 UTC | Aura Console Impacted - Instance View | postmortem | minor | 2 h 05 min |
| 2026-06-30 14:45 UTC | AuraDB issue: Errors when running CREATE VECTOR INDEX | postmortem | minor | 2 h 59 min |
| 2026-06-23 11:25 UTC | Aura console experiencing some intermittent errors | postmortem | minor | 21 h 48 min |
| 2026-05-26 18:23 UTC | Aura Console Auth error | postmortem | major | 4 h 43 min |
| 2026-03-06 10:18 UTC | Console is not available | postmortem | critical | 6 min |
| 2026-03-03 21:35 UTC | Subset of MERGE queries lead to setting unexpected property values | postmortem | none | 17 h 44 min |
| 2026-03-02 19:55 UTC | Middle East Availability - AWS | postmortem | minor | 3 d 20 h |
| 2026-01-26 19:26 UTC | Limited set of queries impacted by Cypher 25 issue | postmortem | minor | 20 h 31 min |
| 2026-01-16 14:25 UTC | Data science feature on AuraDS , AuraDSE and Aura Professional tiers - Native projection affected. | postmortem | minor | 5 h 10 min |
| 2025-11-26 15:47 UTC | Neo4j Aura Service impacted by Resource Shortage in Azure US East | postmortem | major | 14 d 23 h |
| 2025-11-18 15:56 UTC | Pause / Resume / Destroy operations failing | postmortem | minor | 42 min |
| 2025-10-20 16:43 UTC | Several operations degraded for AWS instances in region us-east-1 | postmortem | minor | 4 h 44 min |
| 2025-10-20 09:15 UTC | Aura operations on AWS affected by an incident in US-EAST-1 region | postmortem | minor | 1 h 58 min |
| 2025-08-25 13:34 UTC | Database instance write performance impacted | postmortem | minor | 2 d 3 h |
| 2025-08-22 11:02 UTC | CMI & Instance Operations Unavailable | postmortem | major | 2 h 29 min |
| 2025-08-19 09:19 UTC | Some issues with backups | postmortem | minor | 2 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
}