Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation

What to do

• Check whether you use LaunchDarkly Experiment management, Rollout management, Release pipelines. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 37m it lasted.

  Anything that failed between 2026-10-03 07:29 UTC and 2026-10-03 09:06 UTC may need a replay.

• Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 3

1. identifiedOct 3, 2026, 7: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.

   provider

2. monitoringOct 3, 2026, 8: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.

   provider

3. resolvedOct 3, 2026, 9:06 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.