Rewindex

CompaniesOptimizelyIncidents

Optimizely: Visitor Intelligence incident - EMEA Region

MinorStatus: resolvedStarted Resolved (7 d)1 updatestatus.optimizely.com (opens in new tab)
Part of an outage event

Fastly outage, Jun 8, 2021 · 27 vendors, 27 incidents

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

Swipe sideways to see the whole diagram.

same windowFastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, BrazeOptimizely (this incident)posted +49 min
same windowFastlyown incident not archivedWithin an hour2 vendors, 2 blamed FastlyRubyGems.org, BrazeOptimizely (this incident)posted +49 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["Fastly<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed Fastly<br/>RubyGems.org, Braze"]:::blames
  root --> h1
  me["Optimizely (this incident)<br/>posted +49 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.

Timeline of updates

  1. resolved

    This incident has been resolved. We will continue our investigation to establish the cause. A Post Mortem will be published as soon as it becomes available.

From Optimizely’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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

Optimizely profileRecent Optimizely incidentsMarkdownJSON