Supabase: Database Connection Errors in sa-east-1 and ap-southeast-1
Is it fixed? Yes.
Resolved after 3 h 4 min. First reported Nov 12, 20:35 UTC, resolved Nov 12, 23:40 UTC. The vendor posted it on its status page first.
What happened
Supabase is investigating increased database connection errors affecting the sa-east-1 and ap-southeast-1 regions, where some databases may be unavailable and all services unhealthy.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
This incident was resolved upstream without a reported workaround.
Official fixTimeline
- Investigating(done)
- Workaround available(skipped)
- Resolved(current)
- First report on status page
Database Connection Errors in sa-east-1 and ap-southeast-1
Source - Official statement
Status: Investigating We have observed increased connection errors, some databases may be unavailable with all services unhealthy.
Source - Official statement
⚠️ Supabase is reporting an incident: Database Connection Errors in sa-east-1 and ap-southeast-1 Investigating: Affected components ap-southeast-1 (Degraded performance) sa-east-1 (Degraded performance) t.lpl.dev/QCSwhlZ
Source - Official statement
✅ Resolved: Supabase - Database Connection Errors
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Show all 6 updatesHide the full timeline
- First report on status page
Database Connection Errors in sa-east-1 and ap-southeast-1
Source - Official statement
Status: Investigating We have observed increased connection errors, some databases may be unavailable with all services unhealthy.
Source - Confirmed on Bluesky post
⚠️ Supabase is reporting an incident: Database Connection Errors in sa-east-1 and ap-southeast-1
Source - Official statement
⚠️ Supabase is reporting an incident: Database Connection Errors in sa-east-1 and ap-southeast-1 Investigating: Affected components ap-southeast-1 (Degraded performance) sa-east-1 (Degraded performance) t.lpl.dev/QCSwhlZ
Source - Official statement
✅ Resolved: Supabase - Database Connection Errors
Source - Status changed
Status changed: investigating → resolved (official status page reports resolution).
Evidence
3 reports · 1 Status, 2 BlueskyShow
- [1]Status First reportDatabase Connection Errors in sa-east-1 and ap-southeast-1(opens official status page in a new tab)
Status: Investigating We have observed increased connection errors, some databases may be unavailable with all services unhealthy. Affected components ap-southeast-1 (Degraded performance) sa-east-1 (Degraded performance)
by supabase status
- [2]Bluesky⚠️ Supabase is reporting an incident: Database Connection Errors in sa-east-1 and ap-southeast-1(opens the official status page in a new tab)
⚠️ Supabase is reporting an incident: Database Connection Errors in sa-east-1 and ap-southeast-1 Investigating: Affected components ap-southeast-1 (Degraded performance) sa-east-1 (Degraded performance) t.lpl.dev/QCSwhlZ
by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments96% match
- [3]Bluesky✅ Resolved: Supabase - Database Connection Errors(opens the official status page in a new tab)
✅ Resolved: Supabase - Database Connection Errors
by telescope.littleplanetlabs.comOpens the official status page 1upvotes 0comments86% match
FAQ
What happened in the Supabase outage?
Supabase is investigating increased database connection errors affecting the sa-east-1 and ap-southeast-1 regions, where some databases may be unavailable and all services unhealthy.
What is affected by the Supabase outage?
Supabase.
When did the Supabase outage start and end?
It started Nov 12, 20:35 UTC and was resolved Nov 12, 23:40 UTC, after 3 h 4 min.
How do I get alerts for Supabase?
Subscribe to the Supabase RSS feed for every new Supabase incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Supabase is down. Supabase feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 2 independent sources, including the vendor’s own status page.