LaunchDarkly incident
Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
Resolved after 1 hour 36 minutes, affecting Experiment management and Rollout management and 1 more, on October 3, 2026.
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.
Affected components
Update timeline
- identified Oct 03, 2026, 07:29 AM UTC
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.
- monitoring Oct 03, 2026, 08:51 AM UTC
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.
- resolved Oct 03, 2026, 09:06 AM UTC
This incident has been resolved.
Your product runs on more than LaunchDarkly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.