LaunchDarkly incident

Degraded Observability Ingest

Notice Resolved View vendor source →
Started
Feb 20, 2026, 10:02 PM UTC
Resolved
Feb 20, 2026, 11:04 PM UTC
Duration
1h 1m
Detected by Pingoru
Feb 20, 2026, 10:02 PM UTC

Affected components

OpenTelemetry (Logs, Traces, Metrics)

Update timeline

  1. investigating Feb 20, 2026, 10:02 PM UTC

    Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.

  2. identified Feb 20, 2026, 10:12 PM UTC

    We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.

  3. monitoring Feb 20, 2026, 10:13 PM UTC

    Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.

  4. resolved Feb 20, 2026, 11:04 PM UTC

    Ingest performance has remained stable following mitigation. We are no longer observing impact.

Looking to track LaunchDarkly downtime and outages?

Pingoru polls LaunchDarkly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when LaunchDarkly reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track LaunchDarkly alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring LaunchDarkly for free

5 free monitors · No credit card required