Vendor record
LaunchDarkly
Checked
Front door check counts and LaunchDarkly’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented LaunchDarkly endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- app.launchdarkly.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every LaunchDarkly product, region or your app worked.
How we count front door checksShorter disruptions
Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.
Independent outage detection for LaunchDarkly: Datadog’s Updog(opens in a new tab)CheckUpstream is not affiliated with Datadog.
LaunchDarkly says
Incident posts from LaunchDarkly’s status page, with its titles, impact levels and times. They say what LaunchDarkly chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
34
incidents LaunchDarkly posted, last 1 year
Median recorded duration: 1h 27m. From 34 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 41m)
Elevated error rates in the LaunchDarkly application
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(18h 59m)
Flag delivery errors in Streaming API
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(24m)
Email delivery failure affecting sign-up verification and notification emails
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 19m)
Flag Updates via Polling API delayed
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(5h 33m)
15 older records
Flag Updates delayed in US Region
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(2h 14m)
Elevated errors on server-side SDK streaming connections
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(50m)
Investigating - Known Impact
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(5h 16m)
Delay in Session Replay and Error ingest
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(46m)
LaunchDarkly is operational but customer action may be required
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(18d 23h)
Web application unavailable and flag delivery evaluations have elevated failure rate
CriticalLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 9m)
Launchdarkly UI is down
CriticalLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 33m)
Frequentist experiments cannot be saved or started
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 47m)
High volume of error alerts related to flag delivery network.
MajorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(3h 8m)
Verification emails not being sent
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 27m)
elevated error rates on event data ingestion endpoints
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(1h 40m)
LaunchDarkly.com and LaunchDarkly.com/docs unavailable for some
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(5h 51m)
Observability OpenTelemetry Ingest Delay
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(13m)
Elevated errors affecting LaunchDarkly application requests
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(37m)
Delays in event ingestion
MinorLaunchDarkly’s postStarted, per LaunchDarkly
Closed in our record(4d 17h)
Your code, your dependencies
See which of your code paths call LaunchDarkly
Connect GitHub or GitLab to find where your public or private repository uses LaunchDarkly. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add LaunchDarkly status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is LaunchDarkly currently down?
LaunchDarkly's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did LaunchDarkly last have an outage?
The most recent closed incident record began 14 days ago and spans 18h 59m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for LaunchDarkly?
No. CheckUpstream checks LaunchDarkly’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor LaunchDarkly in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track LaunchDarkly?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.