No impact incident

Supabase: Logs degraded in multiple regions

Oct 30, 2026, 11:38 UTC
started
12:29 UTC
resolved
51 min
duration

Current status of Supabase: Operational — live Supabase status

Timeline

  1. Oct 30, 2026, 11:38 UTC
    investigating
    We are currently investigating degraded Logs functionality in multiple regions. Some users may experience delayed, missing, or unavailable logs in the Dashboard and Logs API. Other services, including your database and APIs, are not affected at this time. Our team is actively investigating. We'll post another update as soon as we have one.
  2. Oct 30, 2026, 11:56 UTC
    identified
    We have identified the cause of the Logs degradation and a fix is being prepared. Other services remain unaffected. We'll post another update as soon as we have one.
  3. Oct 30, 2026, 12:11 UTC
    monitoring
    A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.
  4. Oct 30, 2026, 12:29 UTC
    resolved
    We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption

Updates as published by Supabase.

Other services with incidents at the same time

This was part of a wider event: 16 services reported incidents within the hour.

More Supabase incidents