CompaniesLaunchDarklyIncidents
LaunchDarkly: Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export
Timeline of updates
- resolved
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.
From LaunchDarkly’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.launchdarkly.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by LaunchDarkly, started 2026-02-10 07:30 UTC, resolved after 1.5 h, 1 update(s).
- Title
- Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/incidents/nxjwm5hzjjy3
LaunchDarkly profileRecent LaunchDarkly incidentsAll outages on February 10, 2026LaunchDarkly in February 2026MarkdownJSON