Continuestatus history & uptime

How reliable has Continuebeen? We record a status check every few minutes and keep the history — uptime, recent incidents, and the upstream providers whose outages cascade here. We never invent numbers; where we're still collecting, we say so.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 1m since the last recorded problem.
Operational · 24h
0.00%
0 incidents · ≈1d 0h degraded
288 checks
Operational · 7d
0.05%
0 incidents · ≈6d 23h degraded
2014 checks
Operational · 30d
43.98%
0 incidents · ≈16d 19h degraded
8633 checks
Operational · since Jun 22, 2026
58.02%
0 incidents · ≈16d 19h degraded
11521 checks

% of our checks that found Continue fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow

What cascades to Continue

Continue is built on 7 providers. When one of these has an incident, Continue often degrades too — frequently before its own status page admits it.

History is recorded from Continue's official status plus our own independent checks. AIDownCheck is independent and not affiliated with Continue.