Rewindex

CompaniesNeonIncidents

Neon: ES-1900190

No impact listedStatus: resolvedStarted Resolved (36 min)2 updatesneonstatus.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, May 8, 2026 · 38 vendors, 43 incidents

Neon’s incident names AWS / us-east-1 (location or integration). (hop 1, posted −1 h 30 min vs AWS’s own post)

“…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…”

Swipe sideways to see the whole diagram.

AWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack, Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign, Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreNeon (this incident)posted −1 h 30 min
AWS us-east-1posted 00:25 UTCPosted before AWS did3 vendors, 2 blamed AWSNeon, Datadog, ConvexWithin an hour11 vendors, 11 blamed AWSChargebee, RudderStack,Canva, Logz.io +71 to 4 hours later10 vendors, 9 blamed AWSSalesforce, Dropbox Sign,Klaviyo, HubSpot +6Later2 vendors, 2 blamed AWSWiz, SingleStoreNeon (this incident)posted −1 h 30 min
Neon is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
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

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Database Connectivity

Timeline of updates

  1. monitoring

    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.

  2. resolved

    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.

Impact, status and times are the vendor’s own, as last archived. View on neonstatus.com (opens in new tab).

Neon profileRecent Neon incidentsMarkdownJSON