Supabase: MCP connection error to branch environments
Is it fixed? Yes.
Resolved after <1 min. First reported Aug 11, 18:30 UTC, resolved Aug 11, 18:30 UTC. The vendor posted it on its status page first.
What happened
Customers experienced MCP connection errors when attempting to access branch environments. The incident has since been resolved and services have returned to normal operation.
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(done)
- Archived
Evidence
1 report · 1 StatusShow
- [1]Status First reportMCP connection error to branch environments(opens official status page in a new tab)
Status: Resolved Customers should now be able to connect to branch environments via MCP normally.
by supabase status
FAQ
What happened in the Supabase outage?
Customers experienced MCP connection errors when attempting to access branch environments. The incident has since been resolved and services have returned to normal operation.
What is affected by the Supabase outage?
Supabase.
When did the Supabase outage start and end?
It started Aug 11, 18:30 UTC and was resolved Aug 11, 18:30 UTC, after <1 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 1 report from 1 independent source, including the vendor’s own status page.