LaunchDarkly incident

Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export

Minor Resolved View vendor source →
Started
Feb 10, 2026, 07:30 AM UTC
Resolved
Feb 10, 2026, 09:01 AM UTC
Duration
1h 30m
Detected by Pingoru
Feb 10, 2026, 07:30 AM UTC

Affected components

Observability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)

Update timeline

  1. investigating Feb 10, 2026, 08:42 AM UTC

    Some customers using LaunchDarkly Observability with AWS CloudWatch Metric Stream and/or CloudWatch Firehose log export may experience delayed ingestion of metrics/logs into Observability. The impact is limited to Observability data ingestion and related dashboards/alerts.

  2. resolved Feb 10, 2026, 09:01 AM UTC

    This issue has been resolved. Observability ingestion from AWS CloudWatch Metric Streams and CloudWatch Firehose log export has returned to normal. Data sent during the incident window may not have been ingested, and customers may see gaps in metrics or logs for that period.

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