Issues with Edge Function Deployment

Updates timeline

1. Investigating Jul 30, 05:37 PM UTC

   We are aware of some users experiencing issues with Edge Function deployments.

2. Investigating Jul 30, 06:16 PM UTC

   Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.

3. Investigating Jul 30, 06:28 PM UTC

   We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully.

4. Investigating Jul 30, 07:46 PM UTC

   Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues.

5. Investigating Jul 30, 09:02 PM UTC

   We are continuing to investigate this issue.

6. Investigating Jul 30, 10:21 PM UTC

   We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience.

7. Investigating Jul 30, 11:40 PM UTC

   We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions.

8. Identified Jul 31, 12:26 AM UTC

   The issue has been identified and a fix is being implemented.

9. Monitoring Jul 31, 03:13 AM UTC

   Our fix has completed rollout and we are monitoring for full resolution.

10. Identified Jul 31, 09:36 AM UTC

    We are working on a permanent fix for issue affecting bulk Function deployments. In parallel, we are manually assisting customers who have reported the issue through support tickets.

11. Resolved Jul 31, 01:20 PM UTC

    A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected. As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident. All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation.