Supabase Status · History · Incident #4468
RESOLVEDHigher connection failure rate for ap-northeast-1 and ap-northeast-2
Minor · Started Jun 10, 2026 · 12:00 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 #4468
RESOLVEDMinor · Started Jun 10, 2026 · 12:00 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.
Started
Jun 10, 2026 · 12:00 AM
Resolved
Jun 10, 2026 · 12:00 AM
Duration
< 1m
Severity
None
Event timeline
Resolved
Jun 10 · 1:43 AM SupabaseFrom 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.
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