# LaunchDarkly in October 2019: incidents, uptime and changes

> LaunchDarkly in October 2019: 4 incidents on its status page (1 major or critical), 99.90% 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/2019/10
Last updated: 2019-11-01T00:00:00Z

- Incidents posted: 4 (major/critical: 1) · Maintenance: 0
- By vendor impact label: major 1, minor 3
- Uptime (vendor-reported): 99.90% free of major/critical incidents, 98.79% free of any incident; outage time 43 min, incident time 8 h 59 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [September 2019](https://rewindex.com/company/launchdarkly/2019/09.md) · Next: [November 2019](https://rewindex.com/company/launchdarkly/2019/11.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 |
| --- | --- | --- | --- | --- | --- |
| [LaunchDarkly investigating stale flag data on new client connections](https://rewindex.com/company/launchdarkly/incidents/5x5264th8ht0.md) | major | 2019-10-04 01:49 UTC | 2019-10-04 02:32 UTC | 43 min | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [LaunchDarkly investigating stale flag data on new client connections](https://rewindex.com/company/launchdarkly/incidents/5x5264th8ht0.md) | major | 2019-10-04 01:49 UTC | 2019-10-04 02:32 UTC | 43 min | resolved |
| [Delay in Core Processing](https://rewindex.com/company/launchdarkly/incidents/xlx3dy0bdp49.md) | minor | 2019-10-18 02:24 UTC | 2019-10-18 03:56 UTC | 1.5 h | resolved |
| [Delay in event data processing](https://rewindex.com/company/launchdarkly/incidents/wr4slq8878r3.md) | minor | 2019-10-25 14:24 UTC | 2019-10-25 17:40 UTC | 3.3 h | resolved |
| [Delay in event data processing](https://rewindex.com/company/launchdarkly/incidents/cg4s7mnz30k3.md) | minor | 2019-10-30 01:20 UTC | 2019-10-30 04:48 UTC | 3.5 h | resolved |

## Cite this

LaunchDarkly posted 4 status incidents in October 2019 (1 major or critical); 0 price changes and 0 notable page changes observed.

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


---
Canonical: https://rewindex.com/company/launchdarkly/2019/10 · Markdown: https://rewindex.com/company/launchdarkly/2019/10.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T14:08:34.990Z