Supabase incident

Degraded logs ingestion

Major Resolved View vendor source →
Started
Apr 01, 2026, 12:13 AM UTC
Resolved
Apr 01, 2026, 01:11 AM UTC
Duration
58m
Detected by Pingoru
Apr 01, 2026, 12:13 AM UTC

Affected components

Analytics

Update timeline

  1. investigating Apr 01, 2026, 12:13 AM UTC

    We are seeing degradation of logs and are currently investigating the cause of this issue.

  2. monitoring Apr 01, 2026, 12:47 AM UTC

    We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.

  3. resolved Apr 01, 2026, 01:11 AM UTC

    Log ingestion has recovered and the incident is considered resolved. Some log data was lost during the incident between around 11pm to 11:45pm ETC on March 31.

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
Start monitoring Supabase for free

5 free monitors · No credit card required