Supabase Status · History · Incident #76
RESOLVED403 errors for PostgREST requests
Major · Started Apr 28, 2026 · 9:26 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 #76
RESOLVEDMajor · Started Apr 28, 2026 · 9:26 PM
Duration
2h 4m
Severity
Major
Detection lead
—
User reports
—
Summary
This is now resolved. Thank you for your patience while we worked to resolve this issue.
Started
Apr 28, 2026 · 9:26 PM
Resolved
Apr 28, 2026 · 11:31 PM
Duration
2h 4m
Severity
Major
Event timeline
Investigating
Apr 28 · 9:26 PM SupabaseWe are investigating 403 errors for PostgREST requests across multiple regions.
Identified
Apr 28 · 9:36 PM SupabaseThe issue has been identified and we are working on a fix.
Identified
Apr 28 · 9:40 PM SupabaseWe are continuing to work on a fix for this issue.
Identified
Apr 28 · 10:24 PM SupabaseWe are continuing to work on a fix. We’ll share further updates as progress is made.
Monitoring
Apr 28 · 11:03 PM SupabaseThe exceptions fix has been rolled out, and we are monitoring for continued stability.
Resolved
Apr 28 · 11:31 PM SupabaseThis is now resolved. Thank you for your patience while we worked to resolve this issue.
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