Skip to content

Incident detail

Degraded Log Ingestion

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

    We are investigating a problem with log ingestion. Users may experience delay in current log data.

  2. Identified

    We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.

  3. Identified

    We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.

  4. Identified

    We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.

  5. Monitoring

    Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.

  6. Resolved

    Log ingestion has returned to normal

Keep exploring

More from Supabase

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