rewindex

ChangesNeonES-2331065

Neon: Incident updated: ES-2331065

Incident updateNormal progress (typesafe/jev-1.13-20260917, 59%)Changed neonstatus.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Neon removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: monitoring
ChangedUpdateinvestigating#2
Before: Beginning around 19:30 UTC November 02 2026, customers in AWS US-East-2…
After: Beginning around 17:30 UTC November 02 2026, customers in AWS US-East-2…
AddedUpdateidentified#3
Before: not present
After: Beginning around 17:30 UTC November 02 2026, customers in AWS US-East-2 (Ohio) may encounter slow compute startup times. The cause has been identified and we are seeing recovery.
AddedUpdatemonitoring#4
Before: not present
After: 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. The issue has been mitigated, and we are monitoring to confirm full recovery.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Monday, November 2

2 incident changes

Cite this

Incident updated: ES-2331065 on Neon’s status page, changed 2026-11-02 20:53 UTC (change 1 of 2).

Title
Incident updated: ES-2331065
Vendor
Neon
Date
URL
https://rewindex.com/change/r3459eff397ab19

All Neon changesNeon profileMarkdownJSON