# LaunchDarkly change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [LaunchDarkly](https://rewindex.com/company/launchdarkly.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 9 | 9 | 2026-07-10 17:40 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-07-10 17:40 UTC | Major incident | [Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate](https://rewindex.com/change/iaaf37f20947aed.md) | outage | LaunchDarkly reported a critical incident from 2026-07-10 17:40 UTC to 2026-07-10 18:19 UTC, when it was resolved: app.launchdarkly.com was unavailable and flag-value retrieval had elevated failure rates. Customers using client-side or server-side SDKs should have continued seeing last known flag values where a local cache existed. | | 2026-07-06 20:30 UTC | Major incident | [Major incident: High volume of error alerts related to flag delivery network.](https://rewindex.com/change/icce2100e340c95.md) | outage | LaunchDarkly reported a major outage affecting login and UI/API responsiveness, starting 2026-07-06 20:30 UTC and lasting 51 min until resolution at 2026-07-06 21:21 UTC. The vendor identified a root cause relating to flag delivery, rolled out a fix, and confirmed all error rates had normalized. | | 2026-06-12 04:23 UTC | Major incident | [Major incident: Elevated errors affecting LaunchDarkly application requests](https://rewindex.com/change/i74727a1208b6c9.md) | outage | LaunchDarkly reported major elevated errors affecting some application requests, with authentication, experiment management, flag targeting, progressive rollouts and the web app listed as affected. The incident started at 2026-06-12 04:23 UTC and resolved at 2026-06-12 04:58 UTC (35 min); monitoring confirmed no further impact beyond the initially reported error window. | | 2026-06-03 19:31 UTC | Major incident | [Major incident: Flag dashboard is failing to load](https://rewindex.com/change/i432dc6f546f682.md) | outage | LaunchDarkly’s flag dashboard failed to load in a major-impact outage affecting flag targeting, from 2026-06-03 19:31 UTC to 2026-06-03 20:26 UTC (55 min). A fix was implemented, and LaunchDarkly confirmed the dashboard was successfully loading when the incident was resolved. | | 2026-05-19 14:49 UTC | Major incident | [Major incident: Event Ingestion Delays](https://rewindex.com/change/ic040c3312ab272.md) | degradation | LaunchDarkly reported major event-ingestion delays affecting Experimentation results and Guarded Rollouts, starting 2026-05-19 14:49 UTC and resolving 2026-05-19 14:54 UTC (5 min). No data was lost; the vendor said it identified the root cause and was releasing a fix, then confirmed normal ingestion and full restoration. | | 2026-04-20 22:04 UTC | Major incident | [Critical incident: Docs site is down](https://rewindex.com/change/ie5eef1cd8fcf27.md) | outage | LaunchDarkly’s docs site (launchdarkly.com/docs) was down in a critical-impact incident starting 2026-04-20 22:04 UTC and resolved at 2026-04-20 22:27 UTC, with a reported duration of 22 min. Customers could not access the docs; LaunchDarkly linked the issue to its doc provider’s outage and reported implementing a fix. | | 2026-03-19 16:58 UTC | Major incident | [Major incident: Server-side streaming rejected new connections across all commercial regions](https://rewindex.com/change/i818e8e2d96a6d7.md) | outage | LaunchDarkly reported a major incident affecting new server-side SDK streaming connections across all commercial regions, causing 500/503 errors. Start and resolution were both recorded as 2026-03-19 16:58 UTC, with a computed duration of 0 min. The vendor reported deploying mitigation. | | 2026-02-26 15:43 UTC | Major incident | [Major incident: Investigating Issues with LaunchDarkly Application and Authentication](https://rewindex.com/change/ibbae1ba231a90d.md) | outage | LaunchDarkly reported a major outage affecting some customers’ web app access and authentication from 2026-02-26 15:43 UTC to 2026-02-26 17:06 UTC (1 h 22 min). Some customers also saw low flag-evaluation error counts, but the Flag Delivery Network was generally functional. A fix was implemented, and performance remained stable following mitigation. | | 2026-02-12 23:30 UTC | Major incident | [Major incident: Data attribution issues with Experimentation](https://rewindex.com/change/i02bf148fea8181.md) | degradation | LaunchDarkly reported a major Experimentation degradation starting 2026-02-12 23:30 UTC, lasting 4 h 8 min, with certain experiment iterations receiving incorrectly attributed data. The incident was resolved at 2026-02-13 03:39 UTC; LaunchDarkly confirmed results for active experiments were accurate again. | --- Canonical: https://rewindex.com/company/launchdarkly/changes · Markdown: https://rewindex.com/company/launchdarkly/changes.md · JSON: https://rewindex.com/api/v1/companies/launchdarkly/changes · Generated 2026-10-18T01:29:25.605Z