Supabase incident

MCP connection error to branch environments

Notice Resolved View vendor source →

Supabase experienced a notice incident on August 11, 2026, lasting 3h 52m. The incident has been resolved; the full update timeline is below.

Started
Aug 11, 2026, 02:37 PM UTC
Resolved
Aug 11, 2026, 06:30 PM UTC
Duration
3h 52m
Detected by Pingoru
Aug 11, 2026, 02:37 PM UTC

Update timeline

  1. investigating Aug 11, 2026, 02:37 PM UTC

    We're currently investigating an issue that is impacting MCP connections to branch environments.

  2. identified Aug 11, 2026, 03:09 PM 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.

  3. identified Aug 11, 2026, 03:52 PM UTC

    We're still working on implementing a fix for the identified root cause.

  4. monitoring Aug 11, 2026, 04:33 PM 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.

  5. monitoring Aug 11, 2026, 05:48 PM 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.

  6. resolved Aug 11, 2026, 06:30 PM UTC

    Customers should now be able to connect to branch environments via MCP normally.