Skip to content
LaunchDarkly · Developer toolsFeb 10, 2026, 07:30 UTC

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

MinorNot disclosedUpdated 18h ago
Feb 10, 07:30 UTCFeb 10, 09:01 UTC
Duration
1h 31m
Impact
Minor
Root cause
Not disclosed
LaunchDarkly, 90 days
16 incidents
Affected
Observability Data Ingest (Sessions, Errors)OpenTelemetry (Logs, Traces, Metrics)Observability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability (core functionality) - OpenTelemetry (Logs, Traces, Metrics)
Status page

Final update

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.

Timeline

  1. Resolved · Feb 10, 09:01 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.
  2. Investigating · Feb 10, 07:30 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.

More from LaunchDarkly

Full history

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.