What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with LaunchDarkly now? Check the current statusAffected services
Updates (3)
- Oct 3, 2026, 09:06 AMDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
This incident has been resolved.
LaunchDarkly ↗ - Oct 3, 2026, 08:51 AMDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
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.
LaunchDarkly ↗ - Oct 3, 2026, 07:29 AMDelays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
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.
LaunchDarkly ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow LaunchDarkly's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.