LaunchDarkly Status · History · Incident #6285
RESOLVEDElevated errors on server-side SDK streaming connections
Minor · Started Aug 7, 2026 · 12:29 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'] . '/'; ?>
LaunchDarkly Status · History · Incident #6285
RESOLVEDMinor · Started Aug 7, 2026 · 12:29 PM
Duration
46m
Severity
Minor
Detection lead
—
User reports
—
Summary
SDKs restored to operational
Started
Aug 7, 2026 · 12:29 PM
Resolved
Aug 7, 2026 · 1:15 PM
Duration
46m
Severity
Minor
Event timeline
Investigating
Aug 7 · 12:29 PM LaunchDarklyWe are investigating elevated HTTP 500 errors affecting some server-side SDK streaming connections in our US commercial environment. Affected applications may fail to establish or may intermittently lose their streaming connection to LaunchDarkly.
Investigating
Aug 7 · 12:56 PM LaunchDarklyWe released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.
Investigating
Aug 7 · 1:12 PM LaunchDarklyWe are continuing to investigate this issue.
Resolved
Aug 7 · 1:15 PM LaunchDarklySDKs restored to operational
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. Pulsetic® is a registered trademark.