Supabase · Data and observabilityJul 16, 2026, 17:55 UTC

S3 endpoints for keys with special characters broken

MinorNot disclosedUpdated 47d ago

Jul 16, 17:55 UTCJul 16, 18:49 UTC

Duration

54m

Impact

Minor

Root cause

Not disclosed

Supabase, 90 days

56 incidents

Affected

Storage

Status page

Final update

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.

Timeline

Resolved · Jul 16, 18:49 UTC
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.
Identified · Jul 16, 18:32 UTC
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
Identified · Jul 16, 18:23 UTC
A likely mitigation has been identified and we are discussing the proper implementation method.
Identified · Jul 16, 17:55 UTC
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.

More from Supabase

Full history

NoticeNov 8, 10:53 UTC

Interruption in connections to Supavisor in eu-west-2lasted 1h 42m

MinorNov 6, 23:49 UTC

Increased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28m

MinorNov 5, 23:12 UTC

Intermittent 502/503 errors for pg_net calls to Edge Functionslasted 42m

MinorNov 4, 18:43 UTC

Storage issues in us-east-1 and eu-central-1lasted 16h 18m

MinorNov 4, 03:48 UTC

Intermittent errors on Supavisor Shared Pooler in us-east-2lasted 29m

NoticeNov 3, 04:56 UTC

Management API Postgres config updates overwriting previous updateslasted 2h 8m