Last checked
Optimizely status
A/B testing for web and mobile apps.
Experiencing an issue?
Optimizely宕机了吗？
Degraded performance
Source: official status page
Having issues with Optimizely?
Share your experience to help others stay informed.
Optimizely service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Optimizely activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Optimizely is experiencing issues
Official provider statusOfficial incident active
CMP Analytics Data Not Displaying — Customers using the CMP Analytics module may notice that analytics data for the past 4+ days is not visible in their dashboards. This is a display issue only — all data has been safely recorded and will be backfilled once the fix is deployed.
Official provider status
Optimizely outage reports
0 outage reports in the last 24 hours.
Optimizely 中断地图
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Optimizely 中断地图
Loading report locations…
Optimizely status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- 正常
- 问题
- 中断
- 维护
- 无数据
Optimizely components
| Component name | Status |
|---|
More components are available below.
Optimizely incident history
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 1h 52mOngoing | Yes | Minor | ||
| 7h 18m | Yes | Major | ||
| 2h 49m | Yes | Critical | ||
| 2h 22m | Yes | Minor | ||
| 4h 9m | Yes | Minor | ||
| 6h 1m | Yes | Minor | ||
| 5h 26m | Yes | Minor | ||
| 1h 24m | Yes | Minor |
社区讨论
分享您对 Optimizely 的看法
还没有评论
成为第一个评论的人！
关于 Uptimus 对 Optimizely 的监控
Uptimus 通过官方状态源监控 Optimizely，并将事件、维护和组件健康状况统一为一致的服务状态。
此页面目前包含 174 个受监控组件、75 个事件、53 个维护窗口和 28 天已知历史。
Uptimus 是独立监控服务，与 Optimizely 无关联。健康状态并不保证每位用户、设备或地区都未受影响。
Uptimus 如何监控 Optimizely
当 Optimizely 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。 可用历史包含 75 个事件，为提醒提供当前状态之外的背景。 最近收录的事件是“CMP Analytics Data Not Displaying”。
接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Optimizely 的 174 个组件。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
维护通知
当 Optimizely 发布计划、预定或正在进行的维护时接收通知。 Uptimus 已从 Optimizely 的可用历史中收录 53 个维护窗口。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
