S3 endpoints for keys with special characters broken

Summary

S3 endpoints for keys with special characters broken

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.

• Started

  Jul 16, 2026 · 5:55 PM

• Resolved

  Jul 16, 2026 · 6:49 PM

• Duration

  53m

• Severity

  Minor

• ◆

  Identified

  Jul 16 · 5:55 PM Supabase

  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.

• ◆

  Identified

  Jul 16 · 6:23 PM Supabase

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

• ◆

  Identified

  Jul 16 · 6:32 PM Supabase

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

• ✓

  Resolved

  Jul 16 · 6:49 PM Supabase

  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.