We started checking Neon on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Neon reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Neon's own status page declared. Below it, any public chatter we saw about Neon and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Neon's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Neon in the last 24 hours, which is not evidence that nothing is wrong.
Neon's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Neon's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Neon next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts1 in the last hour (prior day averaged 0.3/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.30%
431
US-West
98.80%
332
Europe
99.67%
303
Asia-Pacific
99.46%
184
Their declared record
Neon's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
ES-2331348Minor incident
Nov 2, 2026, 10:27 PM UTC to Nov 2, 2026, 10:27 PM UTC (0 min)resolved
their latest update (Nov 2, 2026, 10:27 PM UTC): Between 21:45 UTC and 22:11UTC on November 2, 2026, customers may have experienced errors or unavailability across the Neon Console and API, including Project/Branch Operations, Console API, Console Frontend, Account Creation, and Console Login. The issue has been mitigated. Cust…
ES-2331065Minor incident
Nov 2, 2026, 8:33 PM UTC to Nov 2, 2026, 9:01 PM UTC (28 min)resolved
their latest update (Nov 2, 2026, 9:01 PM UTC): Between 17:30 UTC and 19:44 UTC November 02 2026, customers in AWS US-East-2 (Ohio) may have encountered slow compute startup times. This issue is now resolved.
ES-2303481Minor incident
Oct 21, 2026, 6:22 PM UTC to Oct 21, 2026, 7:56 PM UTC (1h 34m)resolved
their latest update (Oct 21, 2026, 7:56 PM UTC): Between 17:20 UTC and 18:42 UTC October 21 2026, an issue with Console Monitoring may have led to delayed or missing monitoring data. This issue is now resolved.
Sep 25, 2026, 6:20 PM UTC to Oct 1, 2026, 3:31 PM UTC (5d 21h)completed
their latest update (Oct 1, 2026, 3:31 PM UTC): This maintenance is now complete and all authentication and login services are performing normally.
Scheduled maintenance of our internal databases.Maintenance
Sep 15, 2026, 1:50 PM UTC to Sep 17, 2026, 1:00 PM UTC (1d 23h)completed
their latest update (Sep 17, 2026, 1:00 PM UTC): Scheduled maintenance is complete.
Scheduled maintenance of our internal databases.Maintenance
Sep 15, 2026, 1:46 PM UTC to Sep 16, 2026, 6:00 PM UTC (1d 4h)completed
their latest update (Sep 16, 2026, 6:00 PM UTC): Scheduled maintenance is complete.
Scheduled maintenance of our internal databases.Maintenance
Sep 15, 2026, 1:44 PM UTC to Sep 16, 2026, 4:00 PM UTC (1d 2h)completed
their latest update (Sep 16, 2026, 4:00 PM UTC): Scheduled maintenance is complete.
Neon Branch Reset and Restore Failures — AWS us-east-2Minor incident
Aug 17, 2026, 10:38 PM UTC to Aug 17, 2026, 10:38 PM UTC (0 min)resolved
their latest update (Aug 17, 2026, 10:38 PM UTC): Between 20:00 UTC and 21:15 UTC on August 17, 2026, a subset of customers using Neon databases in AWS us-east-2 may have experienced delays or failures when performing branch reset and restore operations. A configuration rollout caused these requests to fail on the backend; the N…
Issue with starting computes in us-east-1Minor incident
Aug 10, 2026, 2:53 PM UTC to Aug 10, 2026, 3:02 PM UTC (9 min)resolved
their latest update (Aug 10, 2026, 3:02 PM UTC): Between 14:30 UTC and 14:57 UTC on August 10, 2026, a subset of customers in us-east-1 region may have experienced an unavailability and blocked compute suspension. Startup of new computes and scale from zero was not affected. The issue has been fully resolved, and all services a…
es-2102196Minor incident
Jul 31, 2026, 10:40 AM UTC to Jul 31, 2026, 12:30 PM UTC (1h 50m)resolved
their latest update (Jul 31, 2026, 12:30 PM UTC): Between 14:47 UTC, July 30, 2026, and 12:26 UTC, July 31, 2026, a subset of customers may have experienced errors during account creation. The issue only impacted new account registrations. The issue has been fully resolved, and all services are operating normally. We apologize f…
Showing the 10 most recent of 12 incidents Neon has declared in the history we hold.
These entries are Neon's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Neon's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.