Supabase Status · History · Incident #6328
RESOLVEDMCP connection error to branch environments
Minor · Started Aug 11, 2026 · 2:37 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Supabase Status · History · Incident #6328
RESOLVEDMinor · Started Aug 11, 2026 · 2:37 PM
Duration
3h 52m
Severity
Minor
Detection lead
—
User reports
—
Summary
Customers should now be able to connect to branch environments via MCP normally.
Started
Aug 11, 2026 · 2:37 PM
Resolved
Aug 11, 2026 · 6:30 PM
Duration
3h 52m
Severity
None
Event timeline
Investigating
Aug 11 · 2:37 PM SupabaseWe're currently investigating an issue that is impacting MCP connections to branch environments.
Identified
Aug 11 · 3:09 PM SupabaseWe've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
Identified
Aug 11 · 3:52 PM SupabaseWe're still working on implementing a fix for the identified root cause.
Monitoring
Aug 11 · 4:33 PM SupabaseUPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
Monitoring
Aug 11 · 5:48 PM SupabaseWe 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.
Resolved
Aug 11 · 6:30 PM SupabaseCustomers should now be able to connect to branch environments via MCP normally.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.