checked Oct 30, 2026 11:58 PM UTC · LaunchDarkly's official status page
LaunchDarkly is up and running.
All components operational
Statusfield watches LaunchDarkly alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
7 reports published by LaunchDarkly in the last 30 days · 1 still open
When LaunchDarkly breaks, it is typically resolved in 18h 42m — median across 1 resolved incidents over 30 days.
resolvedOct 26 · 20:52 UTC
A scaling inflection point in our realtime event warehouse led to a delay for some event ingestion. The engineering team has remediated the problem and all events should be caught up. Some customers may have seen delays in experiments and in guarded release processing. This is now resolved and the team will carefully monitor.
Reported by LaunchDarkly on their status page.
ResolvedOct 26 · 20:52 UTC
A scaling inflection point in our realtime event warehouse led to a delay for some event ingestion. The engineering team has remediated the problem and all events should be caught up.Some customers may have seen delays in experiments and in guarded release processing.This is now resolved and the team will carefully monitor.
Reported by LaunchDarkly on their status page.
ScheduledOct 22 · 03:40 UTC
We currently have no indication that LaunchDarkly-hosted services or customer data are impacted by the publicly-disclosed compromised intermediate CA certificates from eMudhra (https://emudhra.we-have-a-problem.com/). This guidance applies to all LaunchDarkly instances: Commercial, EU, and Federal.LaunchDarkly has already taken precautionary steps to secure our platform and has released updated versions of the Relay Proxy and SDKs used by our customers. We continue to monitor the situation and patch all non-critical services.We highly recommend that customers immediately take the following steps to secure the network connection between their systems and LaunchDarkly:- Update LaunchDarkly SDKs and Relay Proxy listed below to the latest version provided- Ensure your application hosts disallow the compromised CAs- Follow publicly-documented remediation steps for your application infrastructure to disallow compromised CAs: https://emudhra.we-have-a-problem.com/LaunchDarkly SDKsOnly the following LaunchDarkly SDKs are affected by this issue and require an update to the versions listed.- Server-side SDK for Python (9.18.3): https://github.com/launchdarkly/python-server-sdk/releases/tag/9.18.3- Server-Side SDK for Erlang/Elixir (3.12.1): https://github.com/launchdarkly/erlang-server-sdk/releases/tag/v3.12.1- OpenFeature provider for the Server-Side SDK for Python (0.8.3): https://github.com/launchdarkly/openfeature-python-server/releases/tag/0.8.3- SDK OTEL integration for the Python server side SDK (1.3.0): https://github.com/launchdarkly/python-server-sdk-otel/releases/tag/1.3.0- Observability and Session Replay SDK for Python (1.3.4): https://github.com/launchdarkly/observability-sdk/releases/tag/launchdarkly-observability-python-1.3.4LaunchDarkly Relay Proxy- Relay Proxy (8.23.2): https://github.com/launchdarkly/ld-relay/releases/tag/v8.23.2- Relay Proxy Helm Chart (3.11.3): https://github.com/launchdarkly/ld-relay-helm/releases/tag/3.11.3We will provide further updates as the situation develops. You can always view our trust center (https://app.vanta.com/launchdarkly.com/trust/gu6fblhdgsyexg8g2xsj0) for the latest updates, as well
Reported by LaunchDarkly on their status page.
resolvedOct 15 · 15:47 UTC
Between 15:11 and 15:32 UTC today, we observed elevated 5xx errors affecting requests across our services. Approximately 0.7% of requests failed during this period (99.3% succeeded). This incident has been resolved.
Reported by LaunchDarkly on their status page.
ResolvedOct 15 · 15:47 UTC
Between 15:11 and 15:32 UTC today, we observed elevated 5xx errors affecting requests across our services. Approximately 0.7% of requests failed during this period (99.3% succeeded). This incident has been resolved.
Reported by LaunchDarkly on their status page.
resolvedOct 3 · 09:06 UTC
This incident has been resolved.
Reported by LaunchDarkly on their status page.
resolvedOct 3 · 09:05 UTC
This incident has been resolved.
Reported by LaunchDarkly on their status page.
