Component of Supabase

Is Supabase Storage down?

Store and serve any type of digital content

Degraded performance

Official timeline

Active incidents naming this component

incidentStorage search failing for restored projects
monitoring
Timeline →

Collected history

Past incidents

IgniteStatus has not collected an incident naming Storage yet. That is the limit of this record, not a claim about Supabase’s history.

Data confidence

Source & freshness

Source: Supabase Status ↗
Collected: Sep 23, 2026, 9:33 AM UTC
Provider updated: Sep 23, 2026, 9:31 AM UTC

Supabase publishes this component separately, so its status can differ from the overall one. Operational means no issue is currently reported for it, not proof that every user or region is unaffected.

While this is open

What should I check next?

Read the incident timeline. The provider updates say what is affected and what they have already ruled out.
Match the affected components against the calls your system actually makes before assuming this incident is yours.
Hold off on rolling back your own deploy. A rollback during a provider incident removes a variable you will want later.
Queue or fail over the work if you can. Aggressive retries against a degraded provider usually make the backlog worse.
Watch the timeline rather than polling the API. It updates as the provider posts, including the resolution.