Skip to content

LaunchDarkly outage history and postmortems

Developer tools · 16 incidents in 90 days · 99.91% implied uptime · last 29d ago

Status page Compare

Incidents

73 on file
StartedIncidentDuration
Aug 2620:00 UTCFlag delivery errors in Streaming API0m
Aug 2412:20 UTCEmail delivery failure affecting sign-up verification and notification emails1h 15m
Aug 1710:36 UTCFlag Updates via Polling API delayed5h 26m
Aug 1414:47 UTCFlag Updates delayed in US Region2h
Aug 719:29 UTCElevated errors on server-side SDK streaming connections46m
Jul 3117:44 UTCInvestigating - Known Impact5h 10m
Jul 2819:24 UTCDelay in Session Replay and Error ingest41m
Jul 2618:32 UTCElevated API Latency and Errors (11:32–11:48 PT)0m
Jul 1017:40 UTCWeb application unavailable and flag delivery evaluations have elevated failure rate39m
Jul 1016:16 UTCLaunchdarkly UI is down and flag evaluation errors are occuring1h 31m
Jul 1016:00 UTCLaunchDarkly is operational but customer action may be required19d 2h
Jul 818:03 UTCFrequentist experiments cannot be saved or started1h 38m
Jul 715:10 UTCDelays in Experimentation and Guarded Rollout results0m
Jul 620:30 UTCHigh volume of error alerts related to flag delivery network.51m
Jul 614:33 UTCVerification emails not being sent1h 19m
Jul 314:29 UTCElevated error rates on event data ingestion endpoints1h 37m
Jun 1719:43 UTCLaunchDarkly.com and LaunchDarkly.com/docs unavailable for some5h 47m
Jun 1517:02 UTCObservability OpenTelemetry Ingest Delay36m
Jun 1204:23 UTCElevated errors affecting LaunchDarkly application requests35m
Jun 912:08 UTCDelays in event ingestion4d 1h
Jun 319:31 UTCFlag dashboard is failing to load55m
May 2218:40 UTCIssue with Slack notifications for Segment approvals1h 2m
May 1914:49 UTCEvent Ingestion Delays5m
May 1600:03 UTCDelayed processing of Session Replay and Error data1h 10m
May 603:58 UTCElevated Streaming Errors in APAC region28m
May 419:47 UTCExperiment and multi-armed bandit results delayed38m
May 410:14 UTCElevated Streaming Errors in Europe6h 8m
May 212:55 UTCDelay in Experimentation Results and Experimentation Warehouse Data Export6h 21m
May 104:06 UTCElevated Server SDK Initialization Errors in APAC region0m
Apr 3011:14 UTCStreaming Data Export Delay44m
Apr 3000:30 UTCErrors on streaming SDK initialization0m
Apr 2920:19 UTCIssue with Experiment Results in case of Flag Variation edits27h 50m
Apr 2818:34 UTCIssues with Observability Alert Notification51m
Apr 2715:39 UTCDelayed Metrics ingest in EU1h 58m
Apr 2319:00 UTCIssue with Warehouse Data Export0m
Apr 2022:04 UTCDocs site is down23m
Apr 2021:27 UTCObservability Alerts are not Delivering Slack Notifications2h 17m
Apr 1004:30 UTCDegraded connectivity for server-side SDKs in EU region0m
Apr 617:58 UTCDelayed processing of Session Replay and Error data1h 3m
Mar 1916:58 UTCServer-side streaming rejected new connections across all commercial regions0m
About LaunchDarkly

The last year, day by day

No incident Minor Major CriticalDeeper colour: longer outage

Downtime, added up

Developer tools median
1h 53m

LaunchDarkly: 1h 53m weighted downtime in range, category median 1h 30m.

16 incidents, 2 major or critical, 7d 20h of incident time (1h 30m major or critical, 7d 19h partial), longest 7d, implied uptime 99.91%, between Jun 28, 2026 and Sep 25, 2026.

Stated causes

71 incidents with no cause stated.

Across fru.dev:Company profileUptime

Questions

Is LaunchDarkly down right now?

Check LaunchDarkly's own status page at https://status.launchdarkly.com for the live state. This page shows LaunchDarkly's incident history from that page; the most recent incident started 2026-08-26: "Flag delivery errors in Streaming API".

How often does LaunchDarkly have outages?

LaunchDarkly posted 16 incidents in the last 90 days and 73 in the last year, 2 of them major or critical in the last 90 days. The median incident lasted 1h 17m.

When was LaunchDarkly's last major outage?

2026-07-10: "Web application unavailable and flag delivery evaluations have elevated failure rate", lasting 39m.

What usually causes LaunchDarkly incidents?

Where LaunchDarkly explained the cause, the most common was configuration change (1 incidents). Most status updates do not name a cause.

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.