# Neon: console.neon.tech is unavailable

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-11-18 12:01 UTC · Resolved: 2025-11-18 17:50 UTC · Duration: 5.8 h
- Updates: 2 · Affected components: Console API, Console Frontend, Console Login
- [Vendor status page: https://neonstatus.com/pages/incident/6878fc85709daa75be6c7e3c/691cb457c96b6604f75ee255](https://neonstatus.com/pages/incident/6878fc85709daa75be6c7e3c/691cb457c96b6604f75ee255)
- [Company: Neon](https://rewindex.com/company/neon.md)

## Part of an outage event

- [Cloudflare outage, Nov 18, 2025: 77 vendors, 81 incidents](https://rewindex.com/events/2025-11-18-cloudflare)
- This incident blames Cloudflare as the cause. (hop 1, posted +31 min vs the first vendor naming Cloudflare)
- Evidence: “…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…”

```mermaid
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
```

_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

- **investigating** 2025-11-18 12:01 UTC: 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
- **resolved** 2025-11-18 17:50 UTC: The issue has been fully resolved. All affected components are operating normally again.


---
Canonical: https://rewindex.com/company/neon/incidents/691cb457c96b6604f75ee255 · Markdown: https://rewindex.com/company/neon/incidents/691cb457c96b6604f75ee255.md · JSON: https://rewindex.com/api/v1/companies/neon/incidents/691cb457c96b6604f75ee255 · Generated 2026-10-20T01:32:01.123Z