LaunchDarkly Status · History · Incident #3742
RESOLVEDDelayed processing of Session Replay and Error data
Minor · Started May 15, 2026 · 5:03 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 #3742
RESOLVEDMinor · Started May 15, 2026 · 5:03 PM
Duration
1h 9m
Severity
Minor
Detection lead
—
User reports
—
Summary
All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.
Started
May 15, 2026 · 5:03 PM
Resolved
May 15, 2026 · 6:13 PM
Duration
1h 9m
Severity
Minor
Event timeline
Investigating
May 15 · 5:03 PM LaunchDarklyWe are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed — no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI.
Identified
May 15 · 5:14 PM LaunchDarklyWe have identified the issue and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.
Resolved
May 15 · 6:13 PM LaunchDarklyAll queued events have been processed and data ingestion is operating normally. No data was lost during this incident.
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