Supabase reports multiple service issues

Project actions have been sustained at normal performance. This incident is resolved.

The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.

We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.

We are testing mitigation options to attempt to restore project action performance.

We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.

Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.

Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.

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.