Supabase incident

Degraded log ingestion

Major Resolved View vendor source →

Supabase experienced a major incident on January 6, 2026 affecting Analytics, lasting 3h 18m. The incident has been resolved; the full update timeline is below.

Started
Jan 06, 2026, 03:31 PM UTC
Resolved
Jan 06, 2026, 06:50 PM UTC
Duration
3h 18m
Detected by Pingoru
Jan 06, 2026, 03:31 PM UTC

Affected components

Analytics

Update timeline

  1. identified Jan 06, 2026, 03:31 PM UTC

    We are seeing degradation in log ingestion in all regions, our engineering team is investigating this issue.

  2. identified Jan 06, 2026, 04:30 PM UTC

    We continue to see degraded log ingestion across all regions. Logflare dashboard may be temporarily unavailable as well while we take steps to mitigate the issue and restore normal service. Our engineering team is actively working on a resolution. We will provide further updates as we make progress.

  3. identified Jan 06, 2026, 04:56 PM UTC

    We have stabilized the ingestion servers. Error rates are back to normal and the Logflare dashboard is functioning. Our team is now working to restore log ingestion for Postgres, PostgREST, and Auth services.

  4. identified Jan 06, 2026, 05:59 PM UTC

    We are continuing to work on restoring full log ingestion for Postgres, PostgREST, and Auth services.

  5. monitoring Jan 06, 2026, 06:23 PM UTC

    Log ingestion has been fully restored across all services. We will continue to monitor the system to ensure stability.

  6. resolved Jan 06, 2026, 06:50 PM UTC

    This incident has been resolved.