CompaniesLaunchDarklyIncidents
LaunchDarkly: Observability Data Delay
Affected components: Observability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability Data Ingest (Sessions, Errors)
Timeline of updates
- investigating
Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.
- identified
We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.
- resolved
We've caught up on the session/error data backlog.
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
7adb410d045a8421…
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-02-19 15:39 UTC, resolved after 30 min, 3 update(s).
- Title
- Observability Data Delay
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/jbgdfj2x2dmh
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on February 19, 2026LaunchDarkly in February 2026MarkdownJSON