Degraded Log Ingestion
Incident Lifecycle
Incident Timeline
Monitoring
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
Mar 27, 2026 at 4:17 PM UTC
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.
Mar 27, 2026 at 4:12 PM UTC
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.
Mar 27, 2026 at 3:52 PM UTC
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.
Mar 27, 2026 at 3:33 PM UTC
Investigating
We are investigating a problem with log ingestion. Users may experience delay in current log data.
Mar 27, 2026 at 3:13 PM UTC
Was your business affected by this Supabase outage?
Set up instant alerts for Supabase — be the first to know about outages via email, Slack, Teams, or Discord.