Supabase incident: S3 endpoints for keys with special characters broken

Affected components

• Storage

1. resolvedJul 16, 2026, 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.

2. identifiedJul 16, 2026, 18:32 UTC

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

3. identifiedJul 16, 2026, 18:23 UTC

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

4. identifiedJul 16, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Linear: Some customers are seeing issues with Linear loadingMajor · Jul 16, 2026, 16:47 UTC
• Inngest: Metrics Data DelaysMajor · Jul 16, 2026, 17:52 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• Akamai: Application Load Balancer reporting availability issuesMinor · Jul 16, 2026, 04:21 UTC
• RevenueCat: App Store Connect degraded performanceMinor · Jul 16, 2026, 13:47 UTC
• Tailscale: Coordination server issuesMinor · Jul 16, 2026, 14:38 UTC
• OneSignal: Journeys - delayed processingMinor · Jul 16, 2026, 15:32 UTC

How often does Supabase have incidents?

Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history