Supabase incident

Degraded Supavisor performance in us-east-1

Notice Resolved View vendor source →
Started
Feb 16, 2026, 11:48 PM UTC
Resolved
Feb 17, 2026, 12:29 AM UTC
Duration
40m
Detected by Pingoru
Feb 16, 2026, 11:48 PM UTC

Update timeline

  1. investigating Feb 16, 2026, 11:48 PM UTC

    Starting from Feb 22:55 UTC, degraded performance in one of our Supavisor clusters resulted in elevated connection latency and increased query p99 response times.

  2. monitoring Feb 17, 2026, 12:16 AM UTC

    We've identified degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times. The problematic node has been replaced and performance is returning to normal levels. We will continue to monitor.

  3. resolved Feb 17, 2026, 12:29 AM UTC

    Performance has returned to normal levels. This incident has been resolved.

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