Vendor reports: operationalResolved · vendor status “resolved”Official status API

Delays in Experimentation and Guarded Rollout results

Reported by LaunchDarkly · Data & Analytics · source last read just now

Vendor start
Jul 7, 2026, 15:10 UTC
Vendor's clock
Resolved
Jul 7, 2026, 15:10 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • LaunchDarkly reports operational: "Delays in Experimentation and Guarded Rollout results".[E1, E2]
  • The vendor marked it resolved at 2026-07-07 15:10 UTC.[E3, E7]

Affected products and regions

  • Components: Data Export, Rollout results processing, Experiment results processing, Rollout results analysis, Experiment results analysis, Warehouse native experimentation.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-07-07 15:10 UTC · summary s1, evidence bd34e60d8b13b7b3

Evidence (7)
  1. E1LaunchDarkly reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delays in Experimentation and Guarded Rollout results". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-07-07 15:10 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Data Export, Rollout results processing, Experiment results processing, Rollout results analysis, Experiment results analysis, Warehouse native experimentation. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-07-07 15:10 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Data Export, Rollout results processing, Experiment results processing, Rollout results analysis, Experiment results analysis, Warehouse native experimentation

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

LaunchDarkly is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 7, 2026, 15:10 UTCVendor-reported startVendor time
  2. Jul 7, 2026, 15:10 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.