Supabase incident: Storage search failing for restored projects

Affected components

• Storage

1. resolvedSep 24, 2026, 10:01 UTC

   Storage is now operating normally. We apologise for the disruption. Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.

2. monitoringSep 23, 2026, 10:20 UTC

   A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.

3. investigatingSep 23, 2026, 09:31 UTC

   We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors. We are working to identify the root cause and will notify for any progress as soon as we have an update

What APIStatus.watch saw

• Sep 24, 2026, 10:40 UTCdegraded → partial outage

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• HashiCorp Vault: HCP Terraform Returning 404sCritical · Sep 23, 2026, 17:43 UTC
• Shippo: Axlehire Shipment and Tracking OutageCritical · Sep 24, 2026, 08:51 UTC
• Grafana Cloud: IRM Access Issues for a Small Group of UsersMajor · Sep 22, 2026, 14:57 UTC
• Fly.io: IPv6 Networking Issues in DFWMajor · Sep 23, 2026, 07:12 UTC
• Amplitude: Export Destinations data delivery issueMajor · Sep 23, 2026, 08:02 UTC
• Sanity: Content Agent - Elevated error ratesMajor · Sep 23, 2026, 10:54 UTC
• Confluent Cloud: Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2Major · Sep 23, 2026, 11:47 UTC
• Fly.io: Upstash unavailability in FRA regionMajor · Sep 23, 2026, 13:07 UTC
• Telnyx: Intermittent 5XX responses on various API endpointsMajor · Sep 23, 2026, 13:49 UTC
• Elasticsearch: Degraded Performance: Cloud Provisioning DelaysMajor · Sep 23, 2026, 14:04 UTC

How often does Supabase have incidents?

Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history