Logs degraded in multiple regions

What to do

• Check whether your product depends on Supabase. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 51m it lasted.

  Anything that failed between 2026-10-30 11:38 UTC and 2026-10-30 12:29 UTC may need a replay.

• Subscribe to Supabase's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Supabase 4

1. investigatingOct 30, 2026, 11:38 AM UTC

   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.

   provider

2. identifiedOct 30, 2026, 11:56 AM UTC

   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.

   provider

3. monitoringOct 30, 2026, 12:11 PM UTC

   A fix has been deployed and we are now monitoring the log service. We'll post another update as soon as we have one.

   provider

4. resolvedOct 30, 2026, 12:29 PM UTC

   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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.