Vendor Status Watch

← all vendors

LaunchDarkly status history

Current state: operational — “All Systems Operational” per https://status.launchdarkly.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
16incidents, last 90 days
50incidents on record
Incidents per week, last 12 weeks:

How long do LaunchDarkly incidents last?

66 minmedian incident duration50 measured
6.3 h90th percentile1 in 10 ran longer
51 minmedian, major/critical only9 incidents

From 50 incidents with a vendor-posted start and resolve time. Longest on record: LaunchDarkly is operational but customer action may be required — 19.1 days (2026-07-10 16:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (50)

StartedIncidentStatusImpactDuration
2026-08-26 19:45 UTCFlag delivery errors in Streaming APIresolvedminor14 min
2026-08-24 12:20 UTCEmail delivery failure affecting sign-up verification and notification emailsresolvedminor1 h 15 min
2026-08-17 10:36 UTCFlag Updates via Polling API delayedresolvedminor5 h 26 min
2026-08-14 14:47 UTCFlag Updates delayed in US Regionresolvedminor2 h 00 min
2026-08-07 19:29 UTCElevated errors on server-side SDK streaming connectionsresolvedminor46 min
2026-07-31 17:44 UTCInvestigating - Known Impactresolvedminor5 h 10 min
2026-07-28 19:24 UTCDelay in Session Replay and Error ingestresolvedminor40 min
2026-07-26 18:32 UTCElevated API Latency and Errors (11:32–11:48 PT)resolvedminor0 min
2026-07-10 17:10 UTCWeb application unavailable and flag delivery evaluations have elevated failure rateresolvedcritical1 h 09 min
2026-07-10 16:16 UTCLaunchdarkly UI is down and flag evaluation errors are occuringresolvednone1 h 31 min
2026-07-10 16:00 UTCLaunchDarkly is operational but customer action may be requiredresolvedminor19 d 2 h
2026-07-08 18:03 UTCFrequentist experiments cannot be saved or startedresolvedminor1 h 38 min
2026-07-07 15:10 UTCDelays in Experimentation and Guarded Rollout resultsresolvednone0 min
2026-07-06 20:30 UTCHigh volume of error alerts related to flag delivery network.resolvedmajor51 min
2026-07-06 14:33 UTCVerification emails not being sentresolvedminor1 h 19 min
2026-07-03 14:29 UTCElevated error rates on event data ingestion endpointsresolvedminor1 h 37 min
2026-06-17 19:43 UTCLaunchDarkly.com and LaunchDarkly.com/docs unavailable for someresolvedminor5 h 46 min
2026-06-15 17:02 UTCObservability OpenTelemetry Ingest Delayresolvedminor36 min
2026-06-12 04:23 UTCElevated errors affecting LaunchDarkly application requestsresolvedmajor35 min
2026-06-08 20:46 UTCDelays in event ingestionresolvedminor4 d 17 h
2026-06-03 19:31 UTCFlag dashboard is failing to loadresolvedmajor55 min
2026-05-22 18:40 UTCIssue with Slack notifications for Segment approvalsresolvednone1 h 01 min
2026-05-19 14:49 UTCEvent Ingestion Delaysresolvedmajor5 min
2026-05-16 00:03 UTCDelayed processing of Session Replay and Error dataresolvedminor1 h 09 min
2026-05-06 03:58 UTCElevated Streaming Errors in APAC regionresolvedminor27 min
2026-05-04 19:47 UTCExperiment and multi-armed bandit results delayedresolvedminor37 min
2026-05-04 10:14 UTCElevated Streaming Errors in Europeresolvedminor6 h 08 min
2026-05-02 12:55 UTCDelay in Experimentation Results and Experimentation Warehouse Data Exportresolvedminor6 h 20 min
2026-05-01 02:52 UTCElevated Server SDK Initialization Errors in APAC regionresolvednone0 min
2026-04-30 11:14 UTCStreaming Data Export Delayresolvedminor43 min
2026-04-29 23:45 UTCErrors on streaming SDK initializationresolvednone0 min
2026-04-29 20:19 UTCIssue with Experiment Results in case of Flag Variation editsresolvedminor27 h 50 min
2026-04-28 18:34 UTCIssues with Observability Alert Notificationresolvedminor51 min
2026-04-27 15:39 UTCDelayed Metrics ingest in EUresolvedminor1 h 58 min
2026-04-23 19:00 UTCIssue with Warehouse Data Exportresolvedminor0 min
2026-04-20 22:04 UTCDocs site is downresolvedcritical22 min
2026-04-20 21:27 UTCObservability Alerts are not Delivering Slack Notificationsresolvedminor2 h 17 min
2026-04-10 04:30 UTCDegraded connectivity for server-side SDKs in EU regionresolvednone0 min
2026-04-06 17:58 UTCDelayed processing of Session Replay and Error dataresolvedminor1 h 03 min
2026-03-19 16:58 UTCServer-side streaming rejected new connections across all commercial regionsresolvedmajor0 min
2026-03-18 02:07 UTCExperiment Data Missing for Some Experiment Iterationsresolvedminor46 h 21 min
2026-03-10 22:59 UTCEvent processing delaysresolvedminor5 h 07 min
2026-03-03 20:40 UTCObservability Usage Reportingresolvednone4 h 32 min
2026-02-26 15:43 UTCInvestigating Issues with LaunchDarkly Application and Authenticationresolvedmajor1 h 22 min
2026-02-20 22:02 UTCDegraded Observability Ingestresolvednone1 h 01 min
2026-02-19 15:39 UTCObservability Data Delayresolvedminor29 min
2026-02-13 00:30 UTCData attribution issues with Experimentationresolvedmajor3 h 08 min
2026-02-11 13:03 UTCObservability – Degraded OTel Telemetry Processingresolvedminor14 h 50 min
2026-02-10 07:30 UTCDegraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Exportresolvedminor1 h 30 min
2026-02-06 11:55 UTCIncreased error rate in our UI and API endpointsresolvedminor49 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch LaunchDarkly with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "launchdarkly"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}