LaunchDarkly Status · History · Incident #4428
RESOLVEDDelays in event ingestion
Minor · Started Jun 8, 2026 · 1: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'] . '/'; ?>
LaunchDarkly Status · History · Incident #4428
RESOLVEDMinor · Started Jun 8, 2026 · 1:46 PM
Duration
4d 17h 6m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Jun 8, 2026 · 1:46 PM
Resolved
Jun 13, 2026 · 6:52 AM
Duration
4d 17h 6m
Severity
Minor
Event timeline
Identified
Jun 8 · 1:46 PM LaunchDarklyWe are currently experiencing delays in event ingestion impacting multiple product areas starting at 12:40pm PT. We have identified the issue and are working on a fix. No data has been lost.
Monitoring
Jun 8 · 2:24 PM LaunchDarklyA fix has been implemented and we are monitoring the results.
Monitoring
Jun 8 · 7:03 PM LaunchDarklyWe are monitoring the status of our services.
Monitoring
Jun 8 · 7:23 PM LaunchDarklyWe are continuing to monitor for any further issues.
Monitoring
Jun 9 · 5:08 AM LaunchDarklyWe have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.
Monitoring
Jun 10 · 11:54 AM LaunchDarklyWe have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.
Monitoring
Jun 10 · 6:31 PM LaunchDarklyWe have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
Monitoring
Jun 10 · 9:07 PM LaunchDarklyWe are continuing to monitor for any further issues.
Monitoring
Jun 10 · 9:07 PM LaunchDarklyWe have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
Monitoring
Jun 10 · 9:12 PM LaunchDarklyWe have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
Monitoring
Jun 10 · 10:14 PM LaunchDarklyWe have made partial progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
Monitoring
Jun 11 · 8:37 AM LaunchDarklyWe have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
Monitoring
Jun 12 · 3:15 PM LaunchDarklyWe have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
Resolved
Jun 13 · 6:52 AM LaunchDarklyThis incident has been resolved.
Pattern
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