Neon lists these components: Database Connectivity, AWS us-east-1.

When did the incident start and end?

It started at 2026-11-13 17:57 UTC. This page shows the end time when Neon marks it resolved.

How do I get alerts for Neon?

Subscribe to the Neon live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Neon. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

NeonIncident ·

Neon Database Connectivity Issues - AWS us-east-1

Q: What happened?

Neon reported "Neon Database Connectivity Issues - AWS us-east-1" on its status page at 2026-11-13 17:57 UTC. Neon database connectivity is degraded in the AWS us-east-1 region. Connections to or queries on databases in that region can fail or time out. Neon reports that the incident is under investigation.

DegradedOfficial update

Neon database connectivity is degraded in the AWS us-east-1 region. Connections to or queries on databases in that region can fail or time out. Neon reports that the incident is under investigation.

State

Investigating

Started

Ongoing for

58 min

Worst impact

Degraded

Timeline

2 updates

17:5718:1118:2518:4018:54

DegradedUpdate postedTimes in UTC

Investigating

58 min 100%

Updates

Times in UTC

As posted by Neon

Investigating

Impact Summary Starting at 13 November 2026 17:20 UTC, Neon database connectivity in the AWS us-east-1 region may fail to connect to or query affected databases. Symptoms Customers may observe: Intermittent errors or timeouts when connecting to databases hosted in the AWS us-east-1 region. Brief connection failures while failover to secondary infrastructure completes. Recommendations No customer action is required at this time. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Investigating

We are actively investigating an issue with a Neon service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Affected components

Database ConnectivityAWS us-east-1

Neon in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

30 min

This incident

1.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

58 min

median 30 min

90 days agoToday

Other Neon incidents

All incidents

Neon·ES-2331065

Neon reports degraded Database Connectivity and Project/Branch Operations in AWS us-east-2. Neon later reported the issue mitigated and monitoring for full recovery. The incident is resolved and lasted 30 minutes.

Resolved

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.live/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.live/feed.xml?providers=neon

Slack

/feed subscribe https://outages.live/feed.xml?providers=neon

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane