A recent API Gateway deployment changed how special characters in S3 object key paths were encoded, causing signature verification failures (403 errors) for storage requests involving those keys. Supabase Storage was affected for approximately 56 minutes. The fix involved reverting the problematic deployment, which resolved the issue.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
A likely mitigation has been identified and we are discussing the proper implementation method.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with