CompaniesLaunchDarklyIncidents
LaunchDarkly: Delay in Session Replay and Error ingest
Affected components: Observability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability Data Ingest (Sessions, Errors)
Timeline of updates
- identified
Customers are experiencing delayed session replay and error ingest as of 11:03am PT. We have identified the issue and are continuing our work to resolve it. Data loss is not expected.
- monitoring
The issue with session replay and error ingest has been identified and a fix has been implemented. We expect to catch up on all backlogged data ingest in ~15 minutes. No data has been lost.
- resolved
The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d5ed7e1a590352c6…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by LaunchDarkly, started 2026-07-28 19:24 UTC, resolved after 41 min, 3 update(s).
- Title
- Delay in Session Replay and Error ingest
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/fjfmh5445cb3
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on July 28, 2026LaunchDarkly in July 2026MarkdownJSON