Incidentsby GlyphMCP connection error to branch environments
Aug 11, 14:37 UTCAug 11, 18:30 UTC
Duration
3h 53m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
Customers should now be able to connect to branch environments via MCP normally.
Timeline
- Resolved · Aug 11, 18:30 UTC
Customers should now be able to connect to branch environments via MCP normally.
- Monitoring · Aug 11, 17:48 UTC
We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
- Monitoring · Aug 11, 16:33 UTC
UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
- Identified · Aug 11, 15:52 UTC
We're still working on implementing a fix for the identified root cause.
- Identified · Aug 11, 15:09 UTC
We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
- Investigating · Aug 11, 14:37 UTC
We're currently investigating an issue that is impacting MCP connections to branch environments.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m