Rewindex

CompaniesNeonIncidents

Neon: console.neon.tech is unavailable

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

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Neon’s incident blames Cloudflare as the cause. (hop 1, posted +31 min vs the first vendor naming Cloudflare)

“…s are currently unable to use to console.neon.tech. Our service is affected by an ongoing Cloudflare network incident affecting reachability across Cloudflare's global network. Cloudflare is actively…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Neon (this incident)posted +31 min
Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Neon (this incident)posted +31 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["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Neon (this incident)<br/>posted +31 min"]:::me
  h1 --- 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: Console APIConsole FrontendConsole Login

Timeline of updates

  1. investigating

    Investigating: (12:01) We are aware of the issue and are investigating the scope, root cause, and potential mitigations. Identified: (12:12) Customers are currently unable to use to console.neon.tech. Our service is affected by an ongoing Cloudflare network incident affecting reachability across Cloudflare's global network. Cloudflare is actively investigating the issue. Our team is monitoring the situation and prepared to restore service immediately once the upstream issue is resolved. In addition to our incident updates, you can follow Cloudflare's at: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We will provide updates as more information becomes available. Monitoring: (13:24) Cloudflare has identified the root cause, have implemented a fix, and are working on restoring all their services. We are observing recovery across our Console service. However, customers in certain regions may still experience higher than normal latency and difficulties logging in to console.neon.tech. We continue to actively monitor the situation and will provide further updates as the issue is fully resolved. Cloudflare status: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. resolved

    The issue has been fully resolved. All affected components are operating normally again.

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 this record existed by then and has not been changed since, by anyone, Rewindex included.

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

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

Neon profileRecent Neon incidentsMarkdownJSON