Resolved after 53 minutes, affecting Storage, on July 16, 2026.
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.
Affected components
Update timeline
- identified Jul 16, 2026, 05:55 PM 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.
- identified Jul 16, 2026, 06:23 PM UTC
A likely mitigation has been identified and we are discussing the proper implementation method.
- identified Jul 16, 2026, 06:32 PM UTC
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
- resolved Jul 16, 2026, 06:49 PM 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.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services