Supabase incident

Intermittent latency in Eastern US

Supabase is currently experiencing a minor incident affecting API Gateway, which began 3d ago. The vendor's full update timeline is below.

Started
Sep 29, 2026, 04:26 PM UTC
Resolved
Ongoing
Duration
● 3d 3h
Detected by Pingoru
Sep 29, 2026, 04:26 PM UTC

Affected components

API Gateway

Update timeline

  1. identified Sep 29, 2026, 04:26 PM 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.

  2. identified Sep 29, 2026, 05:55 PM UTC

    We are continuing our work to fix this latency issue, which has been observed to impacts 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. identified Sep 29, 2026, 09:35 PM 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.

  4. identified Sep 30, 2026, 02:14 AM 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.

  5. identified Sep 30, 2026, 02:54 PM 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.

  6. identified Sep 30, 2026, 09:26 PM 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.

  7. identified Oct 01, 2026, 08:23 PM 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.