Supabase Status · History · Incident #78
RESOLVEDSome Projects Unreachable following Project Restart
Major · Started Apr 27, 2026 · 10:54 AM
$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 #78
RESOLVEDMajor · Started Apr 27, 2026 · 10:54 AM
Duration
9h 11m
Severity
Major
Detection lead
—
User reports
—
Summary
All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.
Started
Apr 27, 2026 · 10:54 AM
Resolved
Apr 27, 2026 · 8:05 PM
Duration
9h 11m
Severity
Major
Event timeline
Identified
Apr 27 · 10:54 AM SupabaseWe’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service.
Identified
Apr 27 · 11:11 AM SupabaseWe’ve identified that a recent change to the Postgres systemd service has a dependency on a prestart script. This script is not present on some older projects, and when those projects restart, Postgres may fail to start successfully. This can result in projects remaining offline. We are working on a fix to restore service. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
Identified
Apr 27 · 11:40 AM SupabaseOur team is actively working on a fix and is manually patching impacted projects to restore service as quickly as possible. If you are running a version of Postgres older than 15.1.1.57, please avoid restarting your project until this issue is resolved.
Monitoring
Apr 27 · 1:12 PM SupabaseAll impacted projects with open support tickets have now been manually patched and restored. We are currently rolling out a fix across the fleet to prevent further impact. We will continue to monitor progress and provide updates.
Identified
Apr 27 · 2:21 PM SupabaseWe’ve identified additional impacted projects and are currently working to manually patch and restore them. We are also continuing to roll out a fix across the fleet to prevent further impact.
Identified
Apr 27 · 4:05 PM SupabaseThe permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.
Monitoring
Apr 27 · 5:31 PM SupabaseThe fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.
Resolved
Apr 27 · 8:05 PM SupabaseAll projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT