How do I check LaunchDarkly status?

Check apistatuscheck.com for real-time LaunchDarkly monitoring on this page, and compare with any official status updates.

Where is the official LaunchDarkly status page?

The official LaunchDarkly status page is https://status.launchdarkly.com. You can also track updates here on API Status Check.

What should I do when LaunchDarkly is down?

Check the official status page, confirm the issue is not local (network or auth), retry with backoff, and subscribe to incident updates while you implement a fallback.

Is LaunchDarkly Down?

Real-time status monitoring

All Systems Operational

30d uptime98.30%

98.30%

Uptime (30d)

70ms

Response Time

Incidents (7d)

7:39:40 AM

Last Checked

As of 3/21/2026, 7:39:40 AM, LaunchDarkly is operational.

⚡ Get notified instantly when LaunchDarkly goes down

Email alerts in under 60 seconds. Never check manually again.

Get Alerts — $9/mo

Embed LaunchDarkly Status Badge

Show live LaunchDarkly status in your README, documentation, or website

Markdown

[![LaunchDarkly Status](https://apistatuscheck.com/api/badge/launchdarkly)](https://apistatuscheck.com/api/launchdarkly)

HTML

<a href="https://apistatuscheck.com/api/launchdarkly"><img src="https://apistatuscheck.com/api/badge/launchdarkly" alt="LaunchDarkly Status" /></a>

Browse all 100 API badges →

Response Time (24h)

Min: 50msMax: 113msAvg: 74ms

113ms57ms0ms

<500ms

500-2000ms

>2000ms

Recent Incidents

minorresolved

Experiment Data Missing for Some Experiment Iterations

Mar 18, 02:07 AM — Resolved Mar 20, 12:29 AM

Our team completed the data restoration for previously affected experiment iterations. Complete data is now available for all experiment iterations in the UI.

majorresolved

Server-side streaming rejected new connections across all commercial regions

Mar 19, 04:58 PM — Resolved Mar 19, 04:58 PM

Server-side streaming began rejecting new connections across all commercial regions, causing 500/503 errors for customers attempting to establish new SDK streaming connections for a brief period of time. Detailed timelines of the incident: - us-east-1 : 7:53 AM PST to 8:24 AM PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.

minorresolved

Event processing delays

Mar 10, 10:59 PM — Resolved Mar 11, 04:07 AM

The issue with Event processing has been resolved. Impacted services have returned to normal operation. Flag Delivery was not impacted. There was no data loss experienced.

noneresolved