Supabase incident: Error spikes in one of the ap-northeast-2 Supavisor clusters

1. resolvedAug 24, 2026, 09:51 UTC

   The issue has been resolved.

2. monitoringAug 24, 2026, 09:13 UTC

   We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.

3. investigatingAug 24, 2026, 07:07 UTC

   We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.

4. investigatingAug 24, 2026, 06:02 UTC

   We are investigating error spikes in the ap-northeast-2 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.

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: Elevated errors for multiple modelsMajor · Aug 24, 2026, 05:06 UTC
• GitHub: Elevated errors on Fable 5 due to upstream providerMajor · Aug 24, 2026, 07:12 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Akamai: Edge Delivery Issues in IndiaMinor · Aug 22, 2026, 11:21 UTC
• Plaid: Elevated API errorsMinor · Aug 24, 2026, 05:36 UTC
• Cursor: Elevated errors for Claude Opus 5Minor · Aug 24, 2026, 05:38 UTC
• ElevenLabs: Media not loading across several productsMinor · Aug 24, 2026, 08:49 UTC
• Zoom: Service Degradation Affecting Meeting Chat ServicesMinor · Aug 24, 2026, 08:56 UTC

How often does Supabase have incidents?

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