LaunchDarkly Status · History · Incident #4739
RESOLVEDLaunchDarkly.com and LaunchDarkly.com/docs unavailable for some
Minor · Started Jun 17, 2026 · 12:43 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 #4739
RESOLVEDMinor · Started Jun 17, 2026 · 12:43 PM
Duration
5h 46m
Severity
Minor
Detection lead
—
User reports
—
Summary
We're now seeing restored access in the affected regions.
Started
Jun 17, 2026 · 12:43 PM
Resolved
Jun 17, 2026 · 6:30 PM
Duration
5h 46m
Severity
Minor
Event timeline
Identified
Jun 17 · 12:43 PM LaunchDarklyLaunchDarkly web application and flag delivery unaffected, but documentation and LaunchDarkly.com are unavailable for some users. A fix is on the way.
Monitoring
Jun 17 · 12:59 PM LaunchDarklyA fix has been implemented and monitoring the results.
Monitoring
Jun 17 · 4:56 PM LaunchDarklyIncident seems to be resolved for the majority of users, however, we are continuing to see some issues for in the San Jose and Los Angeles region. We're working to remediate for these regions.
Monitoring
Jun 17 · 6:23 PM LaunchDarklyWe've identified the source of the problem for areas that were still seeing issues with the LaunchDarkly.com and docs and have a solution in place. We are now monitoring to ensure everything is resolved.
Resolved
Jun 17 · 6:30 PM LaunchDarklyWe're now seeing restored access in the affected regions.
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