Companies / LaunchDarkly / changes
LaunchDarkly change history
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate 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. | Major incident | |
| Major incident: High volume of error alerts related to flag delivery network. 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. | Major incident | |
| Major incident: Elevated errors affecting LaunchDarkly application requests 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. | Major incident | |
| Major incident: Flag dashboard is failing to load 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. | Major incident | |
| Major incident: Event Ingestion Delays 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. | Major incident | |
| Critical incident: Docs site is down 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. | Major incident | |
| Major incident: Server-side streaming rejected new connections across all commercial regions 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. | Major incident | |
| Major incident: Investigating Issues with LaunchDarkly Application and Authentication | Major incident | |
| Major incident: Data attribution issues with Experimentation | Major incident |