Skip to content

Outage tracker / LaunchDarkly

Is LaunchDarkly down?

I'm having a problem

Operationalchecked 1 minute ago

We reached LaunchDarkly from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured LaunchDarkly (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East277 msOperational
US-West555 msOperational
Europe317 msOperational
Asia-Pacific876 msOperational
US-Central59 msOperational
Canada297 msOperational
UK426 msOperational
Southeast Asia1455 msOperational
Australia1239 msOperational
South America513 msOperational
their status pagetheir claim, not our reading

LaunchDarkly reports: All systems operational (“All Systems Operational”)

from LaunchDarkly's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and LaunchDarkly's own status page agree: both show LaunchDarkly as reachable right now.

LaunchDarkly's own component breakdown, as they publish it

  • Audit logOperational
  • AuthenticationOperational
  • Config managementOperational
  • Context processingOperational
  • Emails and notificationsOperational
  • Experiment managementOperational
  • Feature workflowsOperational
  • FrontendOperational
  • Past experiment iterationsOperational
  • Rollout managementOperational
  • Server-side streaming APIOperational
  • Client-side streaming APIOperational
  • Data ExportOperational
  • Flag targetingOperational
  • GraphsOperational
  • Integrations and webhooksOperational
  • MetricsOperational
  • Query APIOperational
  • Rollout results processingOperational
  • Docs (launchdarkly.com/docs)Operational
  • Experiment results processingOperational
  • Expiring Contexts TargetsOperational
  • Flag usage metricsOperational
  • Observability Data Ingest (Sessions, Errors)Operational
  • Playgrounds and offline evaluationsOperational
  • Polling APIOperational
  • Rollout results analysisOperational
  • Segment managementOperational
  • Web app (app.launchdarkly.com)Operational
  • AI insightsOperational
  • Edge APIOperational
  • Experiment results analysisOperational
  • OpenTelemetry (Logs, Traces, Metrics)Operational
  • Progressive rolloutsOperational
  • Website (launchdarkly.com)Operational
  • Release pipelinesOperational
  • Warehouse native experimentationOperational
  • Account managementOperational
  • SDKsOperational

These are LaunchDarkly's components, named and scored by LaunchDarkly. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is LaunchDarkly's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

LaunchDarkly response time, by region

US-East
448msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 633ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 461ms2026-08-25 UTC: p95 616ms2026-08-26 UTC: p95 482ms2026-08-27 UTC: p95 377ms2026-08-28 UTC: p95 383ms2026-08-29 UTC: p95 487ms2026-08-30 UTC: p95 638ms2026-08-31 UTC: p95 710ms2026-09-01 UTC: p95 749ms2026-09-02 UTC: p95 759ms2026-09-03 UTC: p95 490ms2026-09-04 UTC: p95 458ms2026-09-05 UTC: p95 448ms
Aug 7Aug 21Sep 5
US-West
603msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 330ms2026-08-23 UTC: p95 479ms2026-08-24 UTC: p95 455ms2026-08-25 UTC: p95 599ms2026-08-26 UTC: p95 523ms2026-08-27 UTC: p95 863ms2026-08-28 UTC: p95 865ms2026-08-29 UTC: p95 712ms2026-08-30 UTC: p95 718ms2026-08-31 UTC: p95 514ms2026-09-01 UTC: p95 667ms2026-09-02 UTC: p95 565ms2026-09-03 UTC: p95 757ms2026-09-04 UTC: p95 817ms2026-09-05 UTC: p95 603ms
Aug 7Aug 21Sep 5
Europe
596msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 402ms2026-08-23 UTC: p95 755ms2026-08-24 UTC: p95 690ms2026-08-25 UTC: p95 650ms2026-08-26 UTC: p95 775ms2026-08-27 UTC: p95 602ms2026-08-28 UTC: p95 845ms2026-08-29 UTC: p95 632ms2026-08-30 UTC: p95 589ms2026-08-31 UTC: p95 655ms2026-09-01 UTC: p95 901ms2026-09-02 UTC: p95 730ms2026-09-03 UTC: p95 606ms2026-09-04 UTC: p95 563ms2026-09-05 UTC: p95 596ms
Aug 7Aug 21Sep 5
Asia-Pacific
1.5sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.2s2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.5s2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.3s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.3s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 2.1s2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.5s
Aug 7Aug 21Sep 5
US-Central
360msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 414ms2026-09-04 UTC: p95 530ms2026-09-05 UTC: p95 360ms
Aug 7Aug 21Sep 5
Canada
607msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 588ms2026-09-04 UTC: p95 587ms2026-09-05 UTC: p95 607ms
Aug 7Aug 21Sep 5
UK
413msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 647ms2026-09-04 UTC: p95 627ms2026-09-05 UTC: p95 413ms
Aug 7Aug 21Sep 5
Southeast Asia
1.8sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 2.1s2026-09-05 UTC: p95 1.8s
Aug 7Aug 21Sep 5
Australia
1.3sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
South America
784msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 784ms
Aug 7Aug 21Sep 5

Is it LaunchDarkly, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not LaunchDarkly -- it cannot diagnose LaunchDarkly's own systems.

What we measured, function by function

LaunchDarkly answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 277msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach LaunchDarkly normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 555msstatus code: 401checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach LaunchDarkly normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 59msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach LaunchDarkly normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 297msstatus code: 401checked: Sep 5, 2026, 1:53 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach LaunchDarkly normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 513msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach LaunchDarkly normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 317msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach LaunchDarkly normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 426msstatus code: 401checked: Sep 5, 2026, 1:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach LaunchDarkly normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 876msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach LaunchDarkly normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1455msstatus code: 401checked: Sep 5, 2026, 1:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach LaunchDarkly normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1239msstatus code: 401checked: Sep 5, 2026, 1:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach LaunchDarkly normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using LaunchDarkly, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for LaunchDarkly yet, which is not evidence that nothing is wrong.

Recent outages

Flag delivery errors in Streaming API, 1mdeclared on their status page2026-08-26
Email delivery failure affecting sign-up verification and notification emails, 1h 15mdeclared on their status page2026-08-24
Flag Updates via Polling API delayed, 5h 26mdeclared on their status page2026-08-17
Flag Updates delayed in US Region, 2hdeclared on their status page2026-08-14
Elevated errors on server-side SDK streaming connections, 46mdeclared on their status page2026-08-07
Investigating - Known Impact, 5h 10mdeclared on their status page2026-07-31
Delay in Session Replay and Error ingest, 41mdeclared on their status page2026-07-28
Elevated API Latency and Errors (11:32–11:48 PT), 1mdeclared on their status page2026-07-26

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring LaunchDarkly since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for LaunchDarkly covering any window you pick, with our measurements and LaunchDarkly's own claim at the time, side by side.

Full availability history for LaunchDarkly: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching LaunchDarkly, and again when they can reach it again. That is our own measurement from ten regions, not LaunchDarkly's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

LaunchDarkly uptime measured by RealUptimeLive, from this page's own readings.
[![LaunchDarkly uptime measured by RealUptime](https://realuptime.io/outages/launchdarkly/badge.svg?days=30)](https://realuptime.io/outages/launchdarkly)
<a href="https://realuptime.io/outages/launchdarkly"><img src="https://realuptime.io/outages/launchdarkly/badge.svg?days=30" alt="LaunchDarkly uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What LaunchDarkly's SLA implies, from our measurement

At or above your target

We measured none of downtime for LaunchDarkly over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from LaunchDarkly's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://app.launchdarkly.com/api/v2/projects
secondary
https://launchdarkly.com/
secondary
https://status.launchdarkly.com/api/v2/status.json
RealUptime is not affiliated with LaunchDarkly; the name identifies what we measured, and nothing here speaks for LaunchDarkly's own team. We send a single web request to LaunchDarkly from 10 regions on our own schedule and time the response. We do not see inside LaunchDarkly's systems, do not use an account or real transaction, and are not the same signal LaunchDarkly's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for LaunchDarkly is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.