LaunchDarkly incident

Data ingestion delays

Minor Resolved View vendor source →

LaunchDarkly experienced a minor incident on January 31, 2026 affecting Context processing and Flag usage metrics and 1 more component, lasting 2h 18m. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2026, 10:02 AM UTC
Resolved
Jan 31, 2026, 12:20 PM UTC
Duration
2h 18m
Detected by Pingoru
Jan 31, 2026, 10:02 AM UTC

Affected components

Context processingFlag usage metricsObservability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)

Update timeline

  1. investigating Jan 31, 2026, 10:02 AM UTC

    All customers are experiencing data ingestion delays with the following: - Observability sessions and errors - Opentelemetry logs, traces, and metrics - Flag status - Evaluations - Contexts We are investigating and will provide updates as they become available. No data loss is expected.

  2. identified Jan 31, 2026, 10:23 AM UTC

    We have identified the issue and are continuing our work to resolve it.

  3. monitoring Jan 31, 2026, 11:35 AM UTC

    A fix has been implemented and our event processing pipeline for Observability and Opentelemetry are fully caught up. We're continuing to monitor as our event processing pipeline catches up for Flag Status, Evaluations, and Contexts.

  4. resolved Jan 31, 2026, 12:20 PM UTC

    This incident has been resolved and all data processing pipelines are fully caught up. No data was lost.