# Neon: ES-1900190

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-05-07 22:55 UTC · Resolved: 2026-05-07 23:31 UTC · Duration: 36 min
- Updates: 2 · Affected components: Database Connectivity
- [Vendor status page: https://neonstatus.com/pages/incident/6878fc85709daa75be6c7e3c/69fd185bc45d27050d60bcd2](https://neonstatus.com/pages/incident/6878fc85709daa75be6c7e3c/69fd185bc45d27050d60bcd2)
- [Company: Neon](https://rewindex.com/company/neon.md)

## Part of an outage event

- [AWS us-east-1 outage, May 8, 2026: 38 vendors, 43 incidents](https://rewindex.com/events/2026-05-08-aws-us-east-1)
- This incident names AWS / us-east-1 (location or integration). (hop 1, posted −1 h 30 min vs AWS’s own post)
- Evidence: “…een 20:03 UTC and 22:13 UTC on May 7, 2026, a subset of customers using Neon databases in AWS us-east-1 may have experienced issues with compute endpoints not scaling down to zero after periods of ina…”

```mermaid
flowchart LR
  root["AWS us-east-1<br/>posted 00:25 UTC"]:::root
  before["Posted before AWS did<br/>3 vendors, 2 blamed AWS<br/>Neon, Datadog, Convex"]:::blames
  root --> before
  h1["Within an hour<br/>11 vendors, 11 blamed AWS<br/>Chargebee, RudderStack, Canva, Logz.io +7"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>10 vendors, 9 blamed AWS<br/>Salesforce, Dropbox Sign, Klaviyo, HubSpot +6"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Wiz, SingleStore"]:::blames
  root --> later
  me["Neon (this incident)<br/>posted −1 h 30 min"]:::me
  before --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **monitoring** 2026-05-07 22:55 UTC: Starting at 20:03 UTC on May 7, 2026, a subset of customers using Neon databases in AWS us-east-1 may have experienced issues with compute endpoints not scaling down to zero after periods of inactivity. Mitigation has been applied, and affected endpoints are recovering. We are monitoring to confirm full resolution. Customers may have observed:   - Issues starting recently with suspended compute's   - Database compute endpoints not suspending during periods of inactivity   - Unexpected active compute usage for idle databases No customer action is required at this time. We will provide a further update within 1 hour, or sooner if there is a material change in status.
- **resolved** 2026-05-07 23:31 UTC: Between 20:03 UTC and 22:13 UTC on May 7, 2026, a subset of customers using Neon databases in AWS us-east-1 may have experienced issues with compute endpoints not scaling down to zero after periods of inactivity, as well as issues starting recently suspended computes. The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit a support ticket.


---
Canonical: https://rewindex.com/company/neon/incidents/69fd185bc45d27050d60bcd2 · Markdown: https://rewindex.com/company/neon/incidents/69fd185bc45d27050d60bcd2.md · JSON: https://rewindex.com/api/v1/companies/neon/incidents/69fd185bc45d27050d60bcd2 · Generated 2026-10-19T23:15:27.368Z