Skip to content

Incident detail

Intermittent latency in Eastern US

Resolved incidentMinor

Timeline window

to

Get alerted the next time Supabase breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. Resolved

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

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.