Skip to content

Incident detail

Log ingestion impaired

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

    Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.

  2. Identified

    We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.

  3. Identified

    We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.

  4. Identified

    We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.

  5. Identified

    We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.

  6. Monitoring

    The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.

  7. Resolved

    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

Keep exploring

More from Supabase

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