LaunchDarkly status · launchdarkly.com
Is LaunchDarkly Down Today?
Feature flag platform.
No, LaunchDarkly is not down
launchdarkly.com is currently up. Our monitoring probes can reach launchdarkly.com and complete a check without errors. Latest response time was 212 ms. The latest automated check was run 2026-08-14 17:08 UTC from primary location.
- Current status
- Operational
- Last check
- Checked every 10 minutes
- Last 24 hours
- 66.667%
Currently up for 26m
Latest 2026-08-14 17:08 UTC · Primary location
1 incident, 2h 7m down
- Official status
- Operational
- Our check
- Operational
- Active incident
- None
- Last outage
- 2026-08-14
- Response time
- 212 ms
- User reports
- Normal
None today
LaunchDarkly live status
51 of 51 operational
- Account managementOperational
- Agents (core functionality)Operational
- AI insightsOperational
- Audit logOperational
- AuthenticationOperational
- Automations (non-core functionality)Operational
- Client-side streaming APIOperational
- Config managementOperational
- Context processingOperational
- Data ExportOperational
- Docs (launchdarkly.com/docs)Operational
- Edge APIOperational
- Emails and notificationsOperational
- Experiment managementOperational
- Experiment results analysisOperational
- Experiment results processingOperational
- Experimentation (core functionality)Operational
- Experimentation (non-core functionality)Operational
- Expiring Contexts TargetsOperational
- Feature management (core functionality)Operational
- Feature management (non-core functionality)Operational
- Feature workflowsOperational
- Flag Delivery Network (core functionality)Operational
- Flag targetingOperational
- Flag usage metricsOperational
- FrontendOperational
- Global (core functionality)Operational
- Global (non-core functionality)Operational
- GraphsOperational
- Guarded Rollouts (core functionality)Operational
- Integrations and webhooksOperational
- MetricsOperational
- Observability (core functionality)Operational
- Observability Data Ingest (Sessions, Errors)Operational
- OpenTelemetry (Logs, Traces, Metrics)Operational
- Past experiment iterationsOperational
- Playgrounds and offline evaluationsOperational
- Polling APIOperational
- Progressive rolloutsOperational
- Query APIOperational
- Release pipelinesOperational
- Rollout managementOperational
- Rollout results analysisOperational
- Rollout results processingOperational
- SDKsOperational
- Segment managementOperational
- Server-side streaming APIOperational
- Warehouse native experimentationOperational
- Web app (app.launchdarkly.com)Operational
- Website (launchdarkly.com)Operational
- Websites (non-core functionality)Operational
Current incident
No active incidents reported by the official LaunchDarkly status source.
Response time
Latest 154 ms
Loading response-time chart…
Uptime
Availability from independent checks, with recorded incidents and downtime in each window.
Today
66.667%
1 incident, 2h 7m down
Last 7 days
66.667%
1 incident, 2h 7m down
Last 30 days
66.667%
1 incident, 2h 7m down
Last 365 days
66.667%
1 incident, 2h 7m down
Latest LaunchDarkly incidents
Recorded outages with duration and start time.
Last recorded 2026-08-14 14:47 UTC
| Incident | Duration | Started |
|---|---|---|
Flag Updates delayed in US Region Resolved | 2h 7m | 2026-08-14 14:47 UTC |
How this status checker works
Who's Down Today monitors LaunchDarkly independently of the company that runs it. We send reachability checks from our primary location every 10 minutes and record response time, HTTP errors, and timeouts.
When LaunchDarkly publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Frequently asked questions
Is LaunchDarkly down right now?
- No. No, LaunchDarkly is not down. Who's Down Today shows LaunchDarkly as operational based on the latest official signals and independent checks. If you still cannot reach launchdarkly.com, the issue may be local to your connection, DNS, VPN, browser, or device.
Is LaunchDarkly down for everyone or just me?
- Who's Down Today currently shows LaunchDarkly as operational from our monitoring location, which means launchdarkly.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.
What should I do if launchdarkly.com is up but I still cannot access it?
- Try opening launchdarkly.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed LaunchDarkly outage.
How does Who's Down Today check if LaunchDarkly is down?
- We combine independent HTTP reachability checks with public status information where it exists. When LaunchDarkly publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
What does a LaunchDarkly outage mean?
- An outage on this page means recorded incidents or failed checks indicated that LaunchDarkly was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.
Can this page tell me the root cause of a LaunchDarkly outage?
- Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to LaunchDarkly's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.
How do I report an issue with LaunchDarkly?
- Use the report form on this page if LaunchDarkly looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.