LaunchDarkly Status · History · Incident #3832
RESOLVEDEvent Ingestion Delays
Major · Started May 19, 2026 · 7:49 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 #3832
RESOLVEDMajor · Started May 19, 2026 · 7:49 AM
Duration
5m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused. Results were delayed from 6:58am PDT to 7:52am PDT
Started
May 19, 2026 · 7:49 AM
Resolved
May 19, 2026 · 7:54 AM
Duration
5m
Severity
Major
Event timeline
Identified
May 19 · 7:49 AM LaunchDarklyWe are currently experiencing delays in event ingestion, which is impacting Experimentation results and Guarded Rollouts. No data has been lost — all results and events are intact and will be fully accessible once a fix has been deployed. We have identified the root cause and a fix is being released now.
Resolved
May 19 · 7:54 AM LaunchDarklyThis incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused. Results were delayed from 6:58am PDT to 7:52am PDT
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