# LaunchDarkly in May 2020: incidents, uptime and changes

> LaunchDarkly in May 2020: 4 incidents on its status page (2 major or critical), 99.76% free of major or critical incidents (vendor-reported). From Rewindex’s archive of LaunchDarkly’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/launchdarkly/2020/05
Last updated: 2020-06-01T00:00:00Z

- Incidents posted: 4 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, minor 2
- Uptime (vendor-reported): 99.76% free of major/critical incidents, 98.97% free of any incident; outage time 1 h 43 min, incident time 7 h 36 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [April 2020](https://rewindex.com/company/launchdarkly/2020/04.md) · Next: [June 2020](https://rewindex.com/company/launchdarkly/2020/06.md) · [All months](https://rewindex.com/company/launchdarkly/reports.md) · [LaunchDarkly](https://rewindex.com/company/launchdarkly.md)

_Uptime: 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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Polling SDKs are potentially receiving stale flag data](https://rewindex.com/company/launchdarkly/incidents/t89crr1lbyt5.md) | major | 2020-05-21 08:26 UTC | 2020-05-21 09:33 UTC | 1.1 h | resolved |
| [Client connection errors for some clients due to a recent TLS configuration change](https://rewindex.com/company/launchdarkly/incidents/3l8fg0czdfq6.md) | major | 2020-05-30 06:00 UTC | 2020-05-30 06:36 UTC | 36 min | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Elevated errors rates for initialization and polling](https://rewindex.com/company/launchdarkly/incidents/kwzv4ldkmynf.md) | minor | 2020-05-14 23:12 UTC | 2020-05-15 02:41 UTC | 3.5 h | resolved |
| [Polling SDKs are potentially receiving stale flag data](https://rewindex.com/company/launchdarkly/incidents/t89crr1lbyt5.md) | major | 2020-05-21 08:26 UTC | 2020-05-21 09:33 UTC | 1.1 h | resolved |
| [User indexing delayed](https://rewindex.com/company/launchdarkly/incidents/99w1ky27071v.md) | minor | 2020-05-29 02:18 UTC | 2020-05-29 04:42 UTC | 2.4 h | resolved |
| [Client connection errors for some clients due to a recent TLS configuration change](https://rewindex.com/company/launchdarkly/incidents/3l8fg0czdfq6.md) | major | 2020-05-30 06:00 UTC | 2020-05-30 06:36 UTC | 36 min | resolved |

## Cite this

LaunchDarkly posted 4 status incidents in May 2020 (2 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/launchdarkly/2020/05
- Citation: LaunchDarkly, “LaunchDarkly in May 2020” (2020-05-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/launchdarkly/2020/05 (CC BY 4.0).
- Markdown link: `[LaunchDarkly: LaunchDarkly in May 2020 (2020-05-01)](https://rewindex.com/company/launchdarkly/2020/05)`


---
Canonical: https://rewindex.com/company/launchdarkly/2020/05 · Markdown: https://rewindex.com/company/launchdarkly/2020/05.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:52:09.582Z