CheckUpstream measured Optimizely at 100.000% availability across 2039 independent checks (global · api). 17 incidents were recorded in the past 12 months; the most recent resolved 7 days ago after 2 hours. Status signals are polled from Optimizely's official Atlassian Statuspage status page, alongside independent probes and community reports.
90 days measured availability how this is computed
100.000%
global · api · n=2039 · p95 275ms (30d)
Share of our own checks against Optimizely endpoints that returned Optimizely's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 16 incidents · 85 of 90 days with none posted · 6h 6m of declared impact
Fewer incidents in the last 30 days than 11% of 232 tracked services.
Share of each window with no impact declared by Optimizely
7d
100.000%
30d
99.151%
90d
99.717%
180d
99.859%
1y
99.930%
Downtime like this can be refundable
If you're a paying Optimizely customer, outages in these windows may count against Optimizely's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Optimizely entitlement →Does Optimizely actually matter to you?
A Optimizely outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 16 incidents Optimizely published and resolved in the last 90 days, measured between their own start and resolution times. It describes how long Optimizely takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 25, 05:15 UTC · resolved in 2h 25m · Resolved
Aug 25, 05:15 UTC · resolved in 5m · Resolved
Aug 24, 06:53 UTC · resolved in 4h 17m · Resolved
Live Optimizely status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/optimizely)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Optimizely is currently Operational. CheckUpstream tracks Optimizely in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Optimizely down" view? See the Optimizely Live status page.
Aug 24, 06:53 UTC · resolved in 12m · Resolved
Jul 23, 15:26 UTC · resolved in 3h 18m · Resolved
Jul 23, 15:10 UTC · resolved in 5h 29m · Resolved
Jul 23, 06:57 UTC · resolved in 2h 37m · Resolved
Jul 17, 16:59 UTC · resolved in 20m · Resolved
Jul 13, 08:56 UTC · resolved in 1h 54m · Resolved
Jul 9, 18:39 UTC · resolved in 2h 5m · Resolved
Optimizely's last resolved incident started 7 days ago and lasted 2h 25m (degraded performance).
Optimizely's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Optimizely endpoints. It is the share of checks that returned the expected response, not a figure taken from Optimizely's status page.
Sign up to CheckUpstream and add Optimizely to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Optimizely's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.