← Back to Supabase History
minor✓ Resolved

S3 endpoints for keys with special characters broken

Supabase•Thu, Jul 16, 2026, 05:55 PM
Status
resolved
Duration
55 minutes
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Jul 16, 2026, 06:50 PM
This incident has been resolved.
identifiedThu, Jul 16, 2026, 06:32 PM
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
identifiedThu, Jul 16, 2026, 06:23 PM
A likely mitigation has been identified and we are discussing the proper implementation method.
identifiedThu, Jul 16, 2026, 05:55 PM
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.

📊 TECHNICAL DETAILS

Internal ID
081503eb-aa7d-4a9e-b5a9-7815a01b2da7
External ID
5cbt09m9y46n
🕐 Started
Thu, Jul 16, 2026, 05:55 PM
🔄 Last Updated
Thu, Jul 16, 2026, 06:50 PM
✓ Resolved
Thu, Jul 16, 2026, 06:50 PM
MINOR
Impact Level
55 minutes
Total Duration
3
Status Updates
Affected Components
Storage
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed