Supabase incident: Degraded log ingestion

1. resolvedJul 10, 2026, 03:48 UTC

   This issue has been resolved. Log ingestion and log visibility have returned to normal operation. If you experience missing or delayed logs from the affected time period, please contact Support and we'll be happy to assist.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• OVHcloud: [GRA][Network] - Public network incident notificationMajor · Jul 9, 2026, 13:45 UTC
• OVHcloud: [EU-WEST-PAR][Containers & Orchestration] - Loadbalancer/API/Instance provisioning incident notificationMajor · Jul 9, 2026, 20:07 UTC
• Shippo: Australia Post – Delayed Tracking Event UpdatesMinor · Jul 6, 2026, 16:51 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to Liberty Mobile Puerto RicoMinor · Jul 9, 2026, 19:22 UTC
• MongoDB Atlas: Atlas is experiencing issues with issuing certificates from Lets EncryptMinor · Jul 9, 2026, 19:37 UTC
• DigitalOcean: Kubernetes Deployments in NYC1Minor · Jul 9, 2026, 20:31 UTC
• MongoDB Atlas: Atlas Stream Processing is experiencing issues in Azure - West EuropeMinor · Jul 9, 2026, 23:03 UTC

How often does Supabase have incidents?

Supabase reported 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history