LaunchDarkly Status · History · Incident #2364
RESOLVEDElevated Streaming Errors in APAC region
Minor · Started May 5, 2026 · 8:58 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 #2364
RESOLVEDMinor · Started May 5, 2026 · 8:58 PM
Duration
27m
Severity
Minor
Detection lead
—
User reports
—
Summary
We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.
Started
May 5, 2026 · 8:58 PM
Resolved
May 5, 2026 · 9:26 PM
Duration
27m
Severity
Minor
Event timeline
Investigating
May 5 · 8:58 PM LaunchDarklyWe are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
Identified
May 5 · 9:00 PM LaunchDarklyWe're identified an infrastructure issue causing elevated error rates and are working on a fix.
Resolved
May 5 · 9:26 PM LaunchDarklyWe've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.
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