Current answer
Supabase experienced a minor incident: Intermittent latency in Eastern US. ServiceAlert observed recovery on Oct 6, 2026.
Looking for an update now? Check the current status, or follow Supabase for future changes.
Incident Lifecycle
Affected Components
API Gateway
Incident Timeline
Monitoring
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.
Oct 5, 2026 at 6:45 PM UTC
Identified
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.
Oct 2, 2026 at 9:06 PM UTC
Identified
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.
Oct 1, 2026 at 8:23 PM UTC
Identified
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.
We will provide another update as more information becomes available.
Sep 30, 2026 at 9:26 PM UTC
Identified
We're continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they're available.
We will provide updates as soon as they're available.
Sep 30, 2026 at 2:54 PM UTC
Identified
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.
While we do not have an estimated resolution time, we will share updates here as they become available.
Sep 30, 2026 at 2:14 AM UTC
Identified
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.
Sep 29, 2026 at 9:35 PM UTC
Identified
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.
Sep 29, 2026 at 5:55 PM UTC
Identified
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.
We are actively working on a fix. We will provide updates as the fix is implemented.
Sep 29, 2026 at 4:26 PM UTC
Was your business affected by this Supabase outage?
Follow Supabase and route available status alerts to email or a team channel.