Supabase incident
Degraded Logging Ingestion impacting all regions
Affected components
Update timeline
- investigating Mar 23, 2026, 04:28 PM UTC
We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services. Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all. Projects remain fully functional. This issue is limited to logging only. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will provide further updates as more information becomes available.
- identified Mar 23, 2026, 04:38 PM UTC
The cause of the issue has been identified. Our engineering team is working on a fix.
- monitoring Mar 23, 2026, 05:05 PM UTC
A fix has been implemented. The system is now operating normally, and we will continue to monitor.
- resolved Mar 23, 2026, 06:56 PM UTC
This issue is now resolved. All logging ingestion has resumed in all regions.
Looking to track Supabase downtime and outages?
Pingoru polls Supabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Supabase reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Supabase alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required