Live

ES-2331065

0

Neon reports degraded Database Connectivity and Project/Branch Operations in AWS us-east-2. Neon reported slow compute startup times and later confirmed that the issue is mitigated. Neon resolved the incident at 21:03 UTC on November 02 2026, 30 minutes after it started.

State

Resolved

Started

1 h ago

2026-11-02 20:33 UTC

Lasted

30 min

until 2026-11-02 21:03 UTC

Worst impact

Degraded

Timeline

4 updates
20:3320:4020:4820:5521:03
DegradedUpdate postedTimes in UTC

Investigating

30 min 100%

Updates

Times in UTC

As posted by Neon

Resolved2026-11-02 21:03 UTC
Investigating2026-11-02 20:54 UTC

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.

Investigating2026-11-02 20:51 UTC

Beginning around 19: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.

Investigating2026-11-02 20:36 UTC

Beginning around 19:30 UTC November 02 2026, customers in AWS US-East-2 (Ohio) may encounter slow compute startup times. This issue is being actively investigated.

Affected components

3
Database ConnectivityProject/Branch OperationsAWS us-east-2

Neon in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

30 min

This incident

About the median

Follow Neon

Your coding agent knows when Neon is down, and tells you when a failure is theirs, not yours. You can also get Neon incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "neon" and tell me if Neon has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=neon
Slack
/feed subscribe https://outages.cc/feed.xml?providers=neon

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane