Supabase Status · History · Incident #4928
RESOLVEDUpgrade Failures
Minor · Started Jun 25, 2026 · 2:20 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 #4928
RESOLVEDMinor · Started Jun 25, 2026 · 2:20 PM
Duration
4h 31m
Severity
Minor
Detection lead
—
User reports
—
Summary
Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
Started
Jun 25, 2026 · 2:20 PM
Resolved
Jun 25, 2026 · 6:51 PM
Duration
4h 31m
Severity
Minor
Event timeline
Investigating
Jun 25 · 2:20 PM SupabaseWe are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
Investigating
Jun 25 · 2:41 PM SupabaseUpgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
Identified
Jun 25 · 3:01 PM SupabaseThe upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
Identified
Jun 25 · 3:32 PM SupabaseWe are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
Identified
Jun 25 · 4:03 PM SupabaseWe are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.
Identified
Jun 25 · 4:27 PM SupabaseWe are implementing operational mitigations to try to improve upgrade performance.
Identified
Jun 25 · 5:03 PM SupabaseWe are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
Identified
Jun 25 · 5:46 PM SupabaseWe are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.
Monitoring
Jun 25 · 6:08 PM SupabaseWe have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.
Resolved
Jun 25 · 6:51 PM SupabaseThrough our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved.
Pattern
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