Supabase incident

Branch creation degradation

Resolved after 2 hours 39 minutes, on May 21, 2026.

monitoring May 21, 2026, 06:54 PM UTC

Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.

Started
May 21, 2026, 04:46 PM UTC
Resolved
May 21, 2026, 07:26 PM UTC
Duration
2h 39m
Detected by Pingoru
May 21, 2026, 04:46 PM UTC

Update timeline

  1. investigating May 21, 2026, 04:46 PM UTC

    We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.

  2. investigating May 21, 2026, 05:45 PM UTC

    We continue investigating different possible underlying causes and will provide updates as progress is made.

  3. monitoring May 21, 2026, 06:54 PM UTC

    Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.

  4. resolved May 21, 2026, 07:26 PM UTC

    Branch creation continues to be stable.

Your product runs on more than Supabase

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →