Supabase incident

Project Clone Failures (Beta Feature)

Notice Resolved View vendor source →
Started
Feb 03, 2026, 06:42 PM UTC
Resolved
Feb 03, 2026, 09:54 PM UTC
Duration
3h 11m
Detected by Pingoru
Feb 03, 2026, 06:42 PM UTC

Update timeline

  1. investigating Feb 03, 2026, 06:42 PM UTC

    We are currently investigating an issue with our beta project cloning feature (Restore to a New Project). This has been disabled while we conduct our investigations and we will provide an update soon.

  2. identified Feb 03, 2026, 07:56 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 03, 2026, 08:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 03, 2026, 09:54 PM UTC

    This issue is now resolved. Affected customers should delete any failed cloned projects and try again with a new clone.

Looking to track Supabase downtime and outages?

Pingoru polls Supabase's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Supabase reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Supabase alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Supabase for free

5 free monitors · No credit card required