Supabase incident: Network restrictions preventing read replica communication

1. resolvedMay 21, 2026, 04:44 UTC

   Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved.

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: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Twilio: Delay in Getting Twilio/flows Templates Approved on WhatsappMinor · May 18, 2026, 18:42 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• Twilio: SMS Delivery Delays From Twilio to Multiple Networks in Multiple Countries in EuropeMinor · May 19, 2026, 13:21 UTC
• Twilio: SMS Delivery Delays from Twilio Phone Numbers to GTA Wireless United StatesMinor · May 19, 2026, 22:35 UTC
• Twilio: SMS Delivery Failures from Network Subscribers to Twilio Denmark Phone NumbersMinor · May 20, 2026, 07:58 UTC
• Akamai: Configuration Deployment issues with EdgeWorkers and mPulse configuration activationsMinor · May 20, 2026, 14:29 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