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

Digital Experience Platform (DXP) West US

Reported by Optimizely · Data & Analytics · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Jul 23, 2026, 15:10 UTC
Vendor's clock
Resolved
Jul 23, 2026, 20:34 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
5 h 23 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Optimizely reports degraded: "Digital Experience Platform (DXP) West US".[E1, E2]
  • The vendor marked it resolved at 2026-07-23 20:34 UTC.[E3, E7]

Affected products and regions

  • Components: West US.[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-23 20:34 UTC · summary s1, evidence 285a53ba750f4b18

Evidence (7)
  1. E1Optimizely reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Digital Experience Platform (DXP) West US". (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-23 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: West US. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-07-23 20:34 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: West US

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Optimizely 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 23, 2026, 15:10 UTCVendor-reported startVendor time
  2. Jul 23, 2026, 20:34 UTCVendor-reported resolutionVendor time

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