Skip to content
OutageDeck

Incident detail

S3 endpoints for keys with special characters broken

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Supabase breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Supabase alerts work

Timeline

Incident updates

Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.

  1. Identified

    We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.

  2. Identified

    A likely mitigation has been identified and we are discussing the proper implementation method.

  3. Identified

    We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress

  4. Resolved

    This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests.

    The change has been reverted and issue is now fixed.

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.

← Older incident

Projects in stuck state in EU-CENTRAL-1 (Frankfurt)

Newer incident →

Project Actions Failing Across Multiple Regions

All Supabase incidentsSupabase live status