LaunchDarkly incident
Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export
Resolved after 1 hour 30 minutes, affecting Observability Data Ingest (Sessions, Errors) and OpenTelemetry (Logs, Traces, Metrics), on February 10, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than LaunchDarkly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services