Optimizely
No tracked subprocessors.
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Subprocessor list | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| Status page statuspage | snapshot |
Subprocessors
None extracted.
Listed as a subprocessor by (3)
Purposes as each company states them.
InMotion Hosting inmotionhosting.com Improve user experience
Lusha lusha.com A/B Testing Service
Posit posit.co
Service status
- 9 incidents in 35 days
- 3 major or critical
- 2 h 48 min typical time to resolve
- 7 h 18 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Optimizely Graph - USEA production clusters experiencing intermittent availability issues | minor | 2 h 52 min | |
| CMP: Data Not Loading in Plan, Resources, Library, and Other Modules (GCP Stack) | major | 1 h 43 min | |
| Optimizely Identity is redirecting users to the wrong SSO login page. | minor | 3 min | |
| Delay of E-Mails Submitted via SMTP API | minor | 23 min | |
| CMP Analytics Data Not Displaying | minor | 21 h 37 min | |
| SSL trust issue causing login failures across multiple DXP environments | major | 7 h 18 min | |
| CMP and DAM are inaccessible | critical | 2 h 48 min | |
| Service degradation due to network connectivity issue in Southeast Asia | minor | 2 h 21 min |
As Optimizely's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Changes
None since tracking began.