Supabase incident: Log ingestion issues

1. resolvedMay 19, 2026, 00:10 UTC

   This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: SMS Delivery Failures between Twilio Phone Numbers and AT&T in MexicoMinor · May 14, 2026, 20:50 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Snyk: Service Degradation on US-01 (app.snyk.io)Minor · May 18, 2026, 12:12 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 UTC
• Twilio: Delay in Getting Twilio/flows Templates Approved on WhatsappMinor · May 18, 2026, 18:42 UTC
• Twilio: SMS Delivery Failures between Twilio Phone Numbers and Multiple Networks in BrazilMinor · May 18, 2026, 20:36 UTC
• Vercel: Increased Function Invocation Errors - ERR_MODULE_NOT_FOUNDMinor · May 18, 2026, 21:42 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