LaunchDarkly logo

Is LaunchDarkly Down?

Developer ToolsLive status, outages, and incident history

No. LaunchDarkly is up right now.

Every monitored LaunchDarkly system is operational as of October 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment LaunchDarkly breaks

LaunchDarkly is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official LaunchDarkly status page
How we know: the official LaunchDarkly status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

LaunchDarkly Component Status

The main LaunchDarkly systems on this page. All 39 are operational right now.

39operational
Account management
Operational
Agents (core functionality) » AI insights
Operational
Agents (core functionality) » Config management
Operational

36 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Agents (core functionality) » Graphs, Agents (core functionality) » Playgrounds and offline evaluations, Automations (non-core functionality) » Emails and notifications, Automations (non-core functionality) » Expiring Contexts Targets, Automations (non-core functionality) » Integrations and webhooks, Experimentation (core functionality) » Experiment management, Experimentation (core functionality) » Experiment results analysis, Experimentation (core functionality) » Experiment results processing, Experimentation (core functionality) » Warehouse native experimentation, Experimentation (non-core functionality) » Past experiment iterations, Feature management (core functionality) » Feature workflows, Feature management (core functionality) » Flag targeting, and 24 more.

See all of them free

Component statuses may change independently during partial outages.

Recent LaunchDarkly Outages & Incidents

Incident history from the official LaunchDarkly status page, including resolution updates.

Planned Upcoming API Versions RetirementScheduled for Dec 31, 2026 · 8h 0mScheduled

As part of our commitment to reliability and security, LaunchDarkly will retire all API versions except 20240415 on December 31, 2026. After this date, all requests made to retired versions will stop working. To avoid disruption, customers must update integrations and workflows to use version 20240415 before the retirement date. We previously announced the end of life (EOL) for older versions as of April 30, 2025. They have remained available during a grace period, which will end on December 31, 2026 For full details, see our API version changelog: https://launchdarkly.com/docs/api#api-version-changelog Upgrading now ensures uninterrupted access and provides immediate improvements in performance and functionality. We recognize this may be a large undertaking, which is why we are providing extended notice. If you need guidance, please reach out to your account team or contact our support team.

Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and ExperimentationResolved Oct 3, 2026 · 1h 36mResolved

This incident has been resolved. --- [2026-10-03T01:51:43.885-07:00] (monitoring) The backlog of delayed changes has been fully processed as of 1:45 AM PT on October 3. All changes that were delayed during the incident have been applied. No data was lost. We are continuing to monitor. --- [2026-10-03T00:29:12.474-07:00] (identified) Some automatic changes in LaunchDarkly are being applied later than expected. This affects stage transitions for guarded and progressive rollouts, release pipeline phase progression, and multi-armed bandit traffic reallocations. Delays began at approximately 4:15 PM PT on October 2 2026. In-progress rollouts and experiments remain at their current stage and traffic allocation; nothing has been advanced, reverted, or stopped incorrectly. No data is lost. Delayed changes remain queued and will take effect once processing catches up.

Elevated error rates in the LaunchDarkly applicationResolved Oct 2, 2026 · 18h 54mResolved

This incident has been resolved. --- [2026-10-02T18:26:42.073-07:00] (monitoring) Monitoring. We've applied a fix and error rates have returned to normal, including custom role listing, search, and assignment. We're continuing to monitor while we complete recovery work. --- [2026-10-02T10:29:44.811-07:00] (identified) Identified. We've identified the cause of the elevated error rates and are working on a fix. Customers may still be unable to list, search, or assign custom roles; existing roles continue to be enforced. Most other features are operating normally, though some requests may fail intermittently. We'll share another update as recovery progresses. --- [2026-10-02T07:10:59.504-07:00] (identified) We're investigating elevated error rates affecting the LaunchDarkly web application and API. Some requests may fail or time out intermittently, including custom role management. We'll share an update as we learn more.

LaunchDarkly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a LaunchDarkly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Jul 13100.00% average · 6 days with incidentsOct 11

Going further back: LaunchDarkly uptime by month and every recorded LaunchDarkly outage.

Live LaunchDarkly Outage Reports

Problems reported by engineers using LaunchDarkly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No LaunchDarkly problems reported yet.

Something wrong with LaunchDarkly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About LaunchDarkly

LaunchDarkly is a feature management platform enabling teams to control feature flags, run A/B tests, and manage progressive rollouts without redeployment. LaunchDarkly SDK outages can affect feature flag delivery to millions of end users. Track LaunchDarkly status and outages here.

Over the past 30 days, PulsAPI has measured LaunchDarkly uptime at 100.00%. Response times, incident history, and SLA tracking for LaunchDarkly are available on the PulsAPI dashboard.

LaunchDarkly Status FAQ

Is LaunchDarkly down right now?

The verdict at the top of this page comes from the latest poll of the official LaunchDarkly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if LaunchDarkly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until LaunchDarkly recovers.

How do I check LaunchDarkly uptime history?

PulsAPI tracks LaunchDarkly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever LaunchDarkly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect LaunchDarkly outages?

PulsAPI reads the official LaunchDarkly status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual LaunchDarkly components?

Yes. PulsAPI monitors 39 individual LaunchDarkly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when LaunchDarkly goes down?

Yes. Create a free account and subscribe to LaunchDarkly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with LaunchDarkly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot LaunchDarkly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor LaunchDarkly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so LaunchDarkly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track LaunchDarkly with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services