Supabase incident: Degraded performance of the Shared Pooler cluster in ap-southeast-1

1. resolvedJun 24, 2026, 16:14 UTC

   One of the processes in the ap-southeast-1 Supavisor cluster became overloaded, causing difficulties in starting new pools. We restarted a node to stabilize the cluster and scaled the cluster up. The issue appears 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.

• Anthropic: We’ve suspended access to Claude Mythos 5 and Claude Fable 5Critical · Jun 13, 2026, 00:50 UTC
• Snowflake: INC20000052Critical · Jun 24, 2026, 15:38 UTC
• Snyk: Degraded Performance SNYK-US-01Major · Jun 22, 2026, 22:21 UTC
• Smartsheet: Increased spam activity with Smartsheet FormsMinor · Jun 18, 2026, 21:42 UTC
• Snyk: Third-Party Vendor Security Incident (Klue)Minor · Jun 19, 2026, 23:15 UTC
• OVHcloud: [UK1][Public Cloud] - API Incident NotificationMinor · Jun 22, 2026, 14:45 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Orange BotswanaMinor · Jun 24, 2026, 11:45 UTC
• Twilio: User Authentication Identity SNA Failure Increase and Gateway API Failure Increase for EE in United KingdomMinor · Jun 24, 2026, 14:54 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