LaunchDarkly Status · History · Incident #2380
RESOLVEDElevated Streaming Errors in Europe
Minor · Started May 4, 2026 · 3:14 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'] . '/'; ?>
LaunchDarkly Status · History · Incident #2380
RESOLVEDMinor · Started May 4, 2026 · 3:14 AM
Duration
6h 8m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
May 4, 2026 · 3:14 AM
Resolved
May 4, 2026 · 9:23 AM
Duration
6h 8m
Severity
Minor
Event timeline
Investigating
May 4 · 5:28 AM LaunchDarklyWe are investigating elevated error rates for streaming initialization in the Europe region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
Identified
May 4 · 5:51 AM LaunchDarklyWe're identified an infrastructure issue causing elevated error rates and are working on a fix.
Identified
May 4 · 7:30 AM LaunchDarklyWe're continuing to address the root cause of the elevated error rate. Server SDKs may require additional time to initialize while requests are retried.
Monitoring
May 4 · 8:47 AM LaunchDarklyWe've implemented a fix and have mitigated impact as of 8:35am PT. Streaming SDKs should be able to connect successfully at this time.
Resolved
May 4 · 9:23 AM LaunchDarklyThis incident has been resolved.
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