Supabase incident
Degraded Logging Ingestion impacting all regions
Affected components
Update timeline
- investigating Mar 12, 2026, 12:51 PM UTC
We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs. The logs for these services may only be partially ingested. The services remain fully functional, this is only impacting logs. Postgres Logs are not impacted. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will share another update as soon as more information becomes available.
- monitoring Mar 12, 2026, 12:54 PM UTC
A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to normal.
- resolved Mar 12, 2026, 01:53 PM UTC
The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.
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