← Back to Supabase History
minor✓ Resolved

Degraded Log Ingestion

SupabaseFri, Mar 27, 2026, 03:13 PM
Status
resolved
Duration
1h 51m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedFri, Mar 27, 2026, 05:05 PM
This incident has been resolved.
monitoringFri, Mar 27, 2026, 04:17 PM
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
identifiedFri, Mar 27, 2026, 04:12 PM
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.
identifiedFri, Mar 27, 2026, 03:52 PM
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.
identifiedFri, Mar 27, 2026, 03:33 PM
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.
investigatingFri, Mar 27, 2026, 03:13 PM
We are investigating a problem with log ingestion. Users may experience delay in current log data.

📊 TECHNICAL DETAILS

Internal ID
495e06f2-a833-4c7f-b13d-1da0c711a255
External ID
xg8gq2b45wk1
🕐 Started
Fri, Mar 27, 2026, 03:13 PM
🔄 Last Updated
Fri, Mar 27, 2026, 05:05 PM
✓ Resolved
Fri, Mar 27, 2026, 05:05 PM
MINOR
Impact Level
1h 51m
Total Duration
5
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed