Supabase Status · History · Incident #4681
RESOLVEDProject usage analytics API endpoints breakage
Minor · Started Jun 16, 2026 · 3:47 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 #4681
RESOLVEDMinor · Started Jun 16, 2026 · 3:47 PM
Duration
1h 14m
Severity
Minor
Detection lead
—
User reports
—
Summary
All analytics responses have returned to normal.
Started
Jun 16, 2026 · 3:47 PM
Resolved
Jun 16, 2026 · 5:01 PM
Duration
1h 14m
Severity
Minor
Event timeline
Investigating
Jun 16 · 3:47 PM SupabaseWe are investigating a breakage in project usage analytics data propagation.
Investigating
Jun 16 · 4:18 PM SupabaseWe are investigating the components involved in analytics endpoints updates to isolate any changes that could have caused this problem. The issue is limited to the usage.api-requests-count endpoint.
Identified
Jun 16 · 4:22 PM SupabaseThe component at issue has been identified and we are implementing mitigations. Analytics responsiveness on the impacted endpoint is begining to recover.
Monitoring
Jun 16 · 4:27 PM SupabaseThe mitigation has been successful and analytics endpoints are all responsive. We will continue to monitor for stability.
Resolved
Jun 16 · 5:01 PM SupabaseAll analytics responses have returned to normal.
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