Live

Intermittent latency in Eastern US

A fix for this issue has been implemented and our data shows previous impacted users have recovered.

The latest update from Supabase.

State

Resolved

Started

33 d ago

2026-09-29 16:26 UTC

Lasted

7 days

until 2026-10-06 12:15 UTC

Worst impact

Degraded

Timeline

10 updates
Sep 29Oct 1Oct 3Oct 4Oct 6
DegradedUpdate postedDates in UTC

Identified

6 days 89%

Monitoring

17 h 30 min 11%

Updates

Times in UTC

As posted by Supabase

Resolved2026-10-06 12:15 UTC

A fix for this issue has been implemented and our data shows previous impacted users have recovered.

Monitoring2026-10-05 18:45 UTC

A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.

Identified2026-10-02 21:06 UTC

While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.

Identified2026-10-01 20:23 UTC

Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.

Identified2026-09-30 21:26 UTC

We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available.

Identified2026-09-30 14:54 UTC

We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.

Identified2026-09-30 02:14 UTC

We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available.

Identified2026-09-29 21:35 UTC

A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.

Identified2026-09-29 17:55 UTC

We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.

Identified2026-09-29 16:26 UTC

We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.

Supabase in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

27

Median duration

1 h 32 min

This incident

107× the median

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

7 days
median 1 h 32 min
90 days agoToday

Other Supabase incidents

All incidents

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