Is LaunchDarkly down?

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.

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.

Some automatic changes in LaunchDarkly are being applied later than expected. This affects stage transitions for guarded and progressive rollouts, release pipeline phase progression, and multi-armed bandit traffic reallocations. Delays began at approximately 4:15 PM PT on October 2 2026. In-progress rollouts and experiments remain at their current stage and traffic allocation; nothing has been advanced, reverted, or stopped incorrectly. No data is lost. Delayed changes remain queued and will take effect once processing catches up.

The backlog of delayed changes has been fully processed as of 1:45 AM PT on October 3. All changes that were delayed during the incident have been applied. No data was lost. We are continuing to monitor.

This incident has been resolved.

We're investigating elevated error rates affecting the LaunchDarkly web application and API. Some requests may fail or time out intermittently, including custom role management. We'll share an update as we learn more.

Identified. We've identified the cause of the elevated error rates and are working on a fix. Customers may still be unable to list, search, or assign custom roles; existing roles continue to be enforced. Most other features are operating normally, though some requests may fail intermittently. We'll share another update as recovery progresses.

Monitoring. We've applied a fix and error rates have returned to normal, including custom role listing, search, and assignment. We're continuing to monitor while we complete recovery work.

This incident has been resolved.

Server-side streaming requests experienced elevated error rates between approximately 12:00 p.m. and 12:12 p.m. PDT, and some SDKs establishing new streaming connections may have been unable to connect. Polling request error rates remained below 1% throughout the incident. No customer data was lost or compromised. We apologize for the disruption.

This incident has been resolved. Between 12:00 and 12:12 PM PDT on August 26, server-side SDKs establishing new streaming connections experienced elevated error rates. Existing streaming connections were not affected, and polling requests continued to be served with error rates below 1%. The issue was caused by an internal configuration change, which has been reverted. All systems have recovered and are operating normally. No customer data was lost or compromised.