Rewindex

CompaniesOptimizelyIncidents

Optimizely: DXP Management Portal & Configured Commerce - Site Management Degradation in PaaS Portal & Mission Control

MinorStatus: resolvedStarted Resolved (50 min)5 updatesstspg.io (opens in new tab)
Part of an outage event

Meta outage, Jun 12, 2026 · 14 vendors, 14 incidents

Optimizely’s incident started in the same window without naming Meta (timing only, not evidence of a link). (timing only, posted +55 min vs the first vendor naming Meta)

Swipe sideways to see the whole diagram.

same windowMetaown incident not archivedWithin an hour8 vendors, 7 blamed MetaTwilio, Sprout Social, Vonage, Hootsuite +41 to 4 hours later4 vendors, 3 blamed MetaBigCommerce, Braze, Iterable, PlivoOptimizely (this incident)posted +55 min
same windowMetaown incident not archivedWithin an hour8 vendors, 7 blamed MetaTwilio, Sprout Social, Vonage,Hootsuite +41 to 4 hours later4 vendors, 3 blamed MetaBigCommerce, Braze, Iterable,PlivoOptimizely (this incident)posted +55 min
Optimizely is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Meta<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>8 vendors, 7 blamed Meta<br/>Twilio, Sprout Social, Vonage, Hootsuite +4"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed Meta<br/>BigCommerce, Braze, Iterable, Plivo"]:::blames
  root --> h4
  me["Optimizely (this incident)<br/>posted +55 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Digital Experience Cloud Service - Management PortalConfigured Commerce – EMEA RegionConfigured Commerce – NA RegionConfigured Commerce – APAC Region

Timeline of updates

  1. investigating

    We are aware of an ongoing incident with one of our third party vendors that could cause site management-related API calls to fail and/or errors to be displayed. CDN cached traffic and security features are not impacted. We will continue to monitor the situation along with our vendor and will continue to post updates here as they become available.

  2. identified

    Our vendor has confirmed the issue has been identified and a fix is being implemented.

  3. monitoring

    Our vendor has confirmed that a fix has been implemented and they are monitoring the results. We will continue to monitor the situation closely.

  4. monitoring

    System performance should be restored but we will continue to monitor closely.

  5. resolved

    Our vendor has confirmed this issue has been resolved

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Optimizely profileRecent Optimizely incidentsMarkdownJSON