Bubble Status · History · Incident #5377
RESOLVEDLoad Balancer Issues
Critical · Started Jul 9, 2026 · 4:46 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'] . '/'; ?>
Bubble Status · History · Incident #5377
RESOLVEDCritical · Started Jul 9, 2026 · 4:46 PM
Duration
18m
Severity
Critical
Detection lead
—
User reports
Peak 1/hr
Summary
A race condition with our deployment pipeline and ECS cluster caused our load balancer to point to inactive machines. While the current issue is resolved, the incident response team will work on mitigation of future issues of this type.
Started
Jul 9, 2026 · 4:46 PM
Resolved
Jul 9, 2026 · 5:05 PM
Duration
18m
Severity
Critical
Event timeline
Investigating
Jul 9 · 4:46 PM BubbleWe are seeing issues with our load balancer, causing traffic to not be routed properly. We are investigating and will have an ETA for remediation shortly.
Monitoring
Jul 9 · 4:50 PM BubbleLoad balancer and traffic has been restored, and the response team continues to investigate root cause.
Resolved
Jul 9 · 5:05 PM BubbleA race condition with our deployment pipeline and ECS cluster caused our load balancer to point to inactive machines. While the current issue is resolved, the incident response team will work on mitigation of future issues of this type.
User reports · incident window
Hourly report count. Red bars mark the incident window.
Peak: 1 reports/hr
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