outages.live
Live
SupabaseIncident ·

Intermittent errors on Supavisor Shared Pooler in us-east-2

ResolvedOfficial update
0

Supavisor Shared Pooler had intermittent errors in the us-east-2 region. Supabase reports that the incident is resolved. The incident lasted 29 minutes.

State

Resolved

Started

Lasted

29 min

Worst impact

Degraded

Timeline

2 updates
03:4803:5504:0304:1004:17
DegradedUpdate postedTimes in UTC

Monitoring

29 min 100%

Updates

Times in UTC

As posted by Supabase

Resolved

Errors have subsided and connections are back to normal.

Monitoring

Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ``` ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal" ```

Supabase in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

30

Median duration

1 h 22 min

This incident

65% shorter than the median

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

7 days
median 1 h 22 min
90 days agoToday

Other Supabase incidents

All incidents

Supabase·Management API Postgres config updates overwriting previous updates

Supabase reported that Postgres config changes through the Management API only saved the latest values and overwrote earlier changes. Supabase identified the cause, deployed a fix, and disabled some dashboard config changes during the incident. The incident is resolved and lasted 2 hours and 8 minutes.

Resolved

Supabase·Storage uploads failing in us-east-1

Supabase Storage uploads failed with 5xx errors for users in us-east-1. Supabase identified the issue, applied a fix, and monitored the result. The incident is resolved and lasted about 74 minutes.

Resolved

Supabase·PG15 -> PG17 Upgrade Failures

This issue is now resolved.

Resolved

Supabase·Logs degraded in multiple regions

We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption

Resolved

Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC

This issue has been resolved and log delivery is operational again.

Resolved

Follow Supabase

Your coding agent knows when Supabase is down, and tells you when a failure is theirs, not yours. You can also get Supabase 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 "supabase" and tell me if Supabase 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=supabase
Slack
/feed subscribe https://outages.cc/feed.xml?providers=supabase

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane