Live  /  Supabase  /  Incident

Supabase: Storage issues in us-east-1 and eu-central-1

Supabase · supabase.comMinor incidentResolved2026-11-05 11:02 UTC
Public — what happened

Summary

Supabase said some customers in the us-east-1 region were getting server errors when using its Storage service, starting at 18:43 UTC on 4 November 2026, and later said the problem had also affected eu-central-1. The company said it found the cause was tied to heavy load, and that storage responses were back to normal by 20:05 UTC. Supabase then scheduled maintenance on 5 November to raise database capacity for Storage in us-east-1, which it said finished at 08:06 UTC and may have briefly failed some requests while the database switched over. The incident was marked resolved at 11:02 UTC on 5 November, with Storage reported as operating normally in both regions.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Supabase report →

More from Supabase

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.