CompaniesLaunchDarklyMonthly reportsFebruary 2026
LaunchDarkly in February 2026: incidents, uptime and changes
Vendor-reported outage time 5 h 32 min, incident time 23 h 11 min. Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours. Last 90 days.
By vendor label: Major 2 · Minor 4 · No impact listed 1
Major and critical incidents 2
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Data attribution issues with Experimentation | Major | 4.2 h | resolved | 02-12 | |
| Investigating Issues with LaunchDarkly Application and Authentication | Major | 1.4 h | resolved | 02-26 |
Other incidents 5
| Incident | Impact | Started | Duration | Status | Day |
|---|---|---|---|---|---|
| Increased error rate in our UI and API endpoints | Minor | 49 min | resolved | 02-06 | |
| Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export | Minor | 1.5 h | resolved | 02-10 | |
| Observability – Degraded OTel Telemetry Processing | Minor | 15 h | resolved | 02-11 | |
| Observability Data Delay | Minor | 30 min | resolved | 02-19 | |
| Degraded Observability Ingest | No impact listed | 1.0 h | resolved | 02-20 |
Maintenance 1
Show scheduled maintenance
Cite this
LaunchDarkly posted 7 status incidents in February 2026 (2 major or critical); 0 price changes and 0 notable page changes observed.
- Title
- LaunchDarkly in February 2026
- Vendor
- LaunchDarkly
- Date
- URL
- https://rewindex.com/company/launchdarkly/2026/02