Resolved after 1 hour 50 minutes, on March 27, 2026.
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
Update timeline
- investigating Mar 27, 2026, 03:13 PM UTC
We are investigating a problem with log ingestion. Users may experience delay in current log data.
- identified Mar 27, 2026, 03:33 PM UTC
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.
- identified Mar 27, 2026, 03:52 PM UTC
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.
- identified Mar 27, 2026, 04:12 PM UTC
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.
- monitoring Mar 27, 2026, 04:17 PM UTC
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
- resolved Mar 27, 2026, 05:03 PM UTC
Log ingestion has returned to normal
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services