Skip to main content

Supabase outage on September 29, 2026: Intermittent latency in Eastern US

Supabase reported an incident affecting Supabase for 6 days 19 hours on 29 September 2026, from 16:26 to 12:15 UTC.

supabase.com All times UTC

Resolved

Official incident reported by Supabase

Started
16:26
29 Sep 2026 UTC
Resolved
12:15
6 Oct 2026 UTC
Duration
6d 19h
6 days 19 hours
Impact
Minor
as rated by Supabase
Updates
10
posted by Supabase

Timeline

All times UTC.

Official incident from Supabase

Intermittent latency in Eastern US

Resolved Minor impact 29 Sep 2026 16:26 UTC View on Supabase's status page
  1. Official
    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.

  2. Official
    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.

  3. Official
    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.

  4. Official
    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.

  5. Official
    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.

  6. Official
    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.

  7. Official
    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.

  8. Official
    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.

  9. Official
    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.

  10. Official
    Resolved

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

"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.

Does your product depend on Supabase?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.