LaunchDarkly logo - LaunchDarkly status monitoring

Is LaunchDarkly Down?

Real-time status monitoring

All Systems Operational
30d uptime97.99%
97.99%
Uptime (30d)
44ms
Response Time
2
Incidents (7d)
4:52:09 PM
Last Checked

As of 8/3/2026, 4:52:09 PM, LaunchDarkly is operational.

๐Ÿ“ก Monitor LaunchDarkly uptime every 30 seconds โ€” get alerted in under a minute

Trusted by 100,000+ websites ยท Free tier available

Start Free โ†’

โšก Get notified instantly when LaunchDarkly goes down

Email alerts in under 60 seconds. 14-day free trial โ€” $0 today.

Start Free Trial โ†’

Embed LaunchDarkly Status Badge

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

LaunchDarkly Status
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>

Response Time (24h)

Min: 50msMax: 1083msAvg: 142ms
1083ms542ms0ms
<500ms
500-2000ms
>2000ms

Recent Incidents

minorresolved

Investigating - Known Impact

Jul 31, 05:44 PM โ€” Resolved Jul 31, 10:54 PM

The issue with Observability Traces has been resolved. Missing trace data has been recovered.

minorresolved

LaunchDarkly is operational but customer action may be required

Jul 10, 04:00 PM โ€” Resolved Jul 29, 06:15 PM

This incident has been resolved.

minorresolved

Delay in Session Replay and Error ingest

Jul 28, 07:24 PM โ€” Resolved Jul 28, 08:04 PM

The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.

minorresolved

Elevated API Latency and Errors (11:32โ€“11:48 PT)

Jul 26, 06:32 PM โ€” Resolved Jul 26, 06:32 PM

Between 11:32 and 11:48 PT, customers experienced increased latency and elevated error rates on API endpoints. Latency and error rates have returned to normal, and the incident has been resolved.

criticalresolved

Web application unavailable and flag delivery evaluations have elevated failure rate

Jul 10, 05:10 PM โ€” Resolved Jul 10, 06:19 PM

All service availability has been fully restored. Customers using server-side SDKs might need to restart their applications to re-enable the SDKs' connection to LaunchDarkly. Customers using the Relay Proxy may also need to restart their Relay Proxy; in this case, the Relay Proxy should be restarted before restarting their applications that connect to it. To determine if an application needs to be restarted, customers can look at their application logs. Affected SDKs will emit (depending on language) logs containing one of "giving up permanently", "Invalid SDK key", "unauthorized", or "not authorized", or "401". Services which emitted logs such as these before 9:13AM PT may be unable to receive flag updates and will be unable to send events to LaunchDarkly until they are restarted.

Get LaunchDarkly Outage Alerts

Be the first to know when LaunchDarkly go down.

Alert Pro

14-day free trial

Stop checking โ€” get alerted instantly

Next time LaunchDarkly goes down, you'll know in under 60 seconds โ€” not when your users start complaining.

  • Email alerts for LaunchDarkly + 9 more APIs
  • $0 due today for trial
  • Cancel anytime โ€” $9/mo after trial

What is LaunchDarkly?

Feature flag management platform for controlled software releases

LaunchDarkly Down? Try These Steps

  1. Check the official LaunchDarkly status page for announcements
  2. Try refreshing your browser or clearing cache
  3. Check your internet connection
  4. Try accessing from a different network or VPN
  5. Check social media for reports from other users
  6. Set up automated monitoring so you know before your users do โ€” Better Stack monitors every 30 seconds

Is LaunchDarkly down for everyone or just me?

To determine whether it's a widespread LaunchDarkly outage or a problem specific to your account or location:

  1. Check the status indicator above โ€” if this page shows a major outage, it's confirmed global.
  2. Try a different device or network โ€” if it works on mobile data but not Wi-Fi, it's likely a local network issue, not LaunchDarkly.
  3. Clear cache and cookies โ€” browser issues can mimic service outages.
  4. Check community reports โ€” Downdetector and social media will show whether hundreds of other users are reporting the same issue.
  5. Test the API directly (for developers) โ€” a raw request returning 5xx errors confirms a service-side outage; a 429 means you've hit your personal rate limit.

Official source: LaunchDarkly Status Page

โฑ๏ธ

The average API outage costs $5,600 per minute

Gartner estimates downtime costs $5,600/min on average. 98% of organizations say a single hour of downtime costs over $100,000. Proactive monitoring catches issues in under 30 seconds.

๐Ÿ”ง Recommended Tools

1
Monitor before it breaksMost Important

Know when LaunchDarkly goes down before your users complain. 30-second checks, instant alerts.

Trusted by 100,000+ websites ยท Free tier available

Better Stack โ€” Start Free
2
Secure your API keys

Manage API keys, database passwords, and service tokens securely. Rotate automatically when breaches occur.

Trusted by 150,000+ businesses ยท From $2.99/mo

1Password โ€” Try Free
3
Automate your status checks

Monitor LaunchDarkly and 100+ APIs with instant email alerts. 14-day free trial.

๐Ÿ“–

Complete LaunchDarkly Troubleshooting Guide

In-depth guide with step-by-step troubleshooting, common error codes, workarounds, and what to do during LaunchDarkly outages.

Read the full guide

Never get caught off guard by an outage

Get instant email alerts when APIs go down. Monitor up to 10 APIs for $9/mo โ€” that's less than 1 minute of downtime costs.

14-day free trial. $0 due today. Cancel anytime.