Supabase Status · History · Incident #6057
RESOLVEDIssues with Edge Function Deployment
Major · Started Jul 30, 2026 · 5:37 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Supabase Status · History · Incident #6057
RESOLVEDMajor · Started Jul 30, 2026 · 5:37 PM
Duration
19h 42m
Severity
Major
Detection lead
—
User reports
—
Summary
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. Support will continue working directly with customers whose existing deployments require remediation.
Started
Jul 30, 2026 · 5:37 PM
Resolved
Jul 31, 2026 · 1:20 PM
Duration
19h 42m
Severity
Major
Event timeline
Investigating
Jul 30 · 5:37 PM SupabaseWe are aware of some users experiencing issues with Edge Function deployments.
Investigating
Jul 30 · 6:16 PM SupabaseOnly a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.
Investigating
Jul 30 · 6:28 PM SupabaseWe 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.
Investigating
Jul 30 · 7:46 PM SupabasePer-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.
Investigating
Jul 30 · 9:02 PM SupabaseWe are continuing to investigate this issue.
Investigating
Jul 30 · 10:21 PM SupabaseWe 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.
Investigating
Jul 30 · 11:40 PM SupabaseWe 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.
Identified
Jul 31 · 12:26 AM SupabaseThe issue has been identified and a fix is being implemented.
Monitoring
Jul 31 · 3:13 AM SupabaseOur fix has completed rollout and we are monitoring for full resolution.
Identified
Jul 31 · 9:36 AM SupabaseWe 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.
Resolved
Jul 31 · 1:20 PM SupabaseA 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. Support will continue working directly with customers whose existing deployments require remediation.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.