# LaunchDarkly in January 2026: incidents, uptime and changes

> LaunchDarkly in January 2026: 4 incidents on its status page (0 major or critical), 100% 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/2026/01
Last updated: 2026-02-01T00:00:00Z

- Incidents posted: 4 (major/critical: 0) · Maintenance: 1
- By vendor impact label: minor 4
- Uptime (vendor-reported): 100% free of major/critical incidents, 98.41% free of any incident; outage time 0 min, incident time 11 h 47 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [December 2025](https://rewindex.com/company/launchdarkly/2025/12.md) · Next: [February 2026](https://rewindex.com/company/launchdarkly/2026/02.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._

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Guarded releases event ingestion delays](https://rewindex.com/company/launchdarkly/incidents/0yr1kv8n87g9.md) | minor | 2026-01-08 18:46 UTC | 2026-01-08 22:00 UTC | 3.2 h | resolved |
| [Unable to edit JSON flag variations](https://rewindex.com/company/launchdarkly/incidents/83cdyc5yb0s0.md) | minor | 2026-01-12 17:48 UTC | 2026-01-12 19:44 UTC | 1.9 h | resolved |
| [Elevated error rate when configuring Okta SCIM](https://rewindex.com/company/launchdarkly/incidents/hwqdw472s8qb.md) | minor | 2026-01-26 17:54 UTC | 2026-01-26 22:13 UTC | 4.3 h | resolved |
| [Data ingestion delays](https://rewindex.com/company/launchdarkly/incidents/qty231hgv0d2.md) | minor | 2026-01-31 10:02 UTC | 2026-01-31 12:20 UTC | 2.3 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] IP address updates for events.launchdarkly.com](https://rewindex.com/company/launchdarkly/incidents/wy3jccg50r43.md) | maintenance | 2026-01-08 23:29 UTC | not resolved | ongoing | unknown |

## Cite this

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

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


---
Canonical: https://rewindex.com/company/launchdarkly/2026/01 · Markdown: https://rewindex.com/company/launchdarkly/2026/01.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T11:03:16.410Z