Continue outage history

We record Continue's status every five minutes and have not recorded an incident from Continue's status page yet. We never invent one.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 3m since the last recorded problem.
Operational · 24h
0.00%
0 incidents · ≈1d 0h degraded
288 checks
Operational · 7d
0.00%
0 incidents · ≈6d 23h degraded
2015 checks
Operational · 30d
0.01%
0 incidents · ≈29d 23h degraded
8638 checks
Operational · since Jun 22, 2026
16.23%
0 incidents · ≈1h 5m down · ≈119d 20h degraded
41216 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

How Continue fails

Since Jun 29, 2026, Continue's status page has marked one Continue component as impaired, across 34,516 of our five-minute readings. Continue Hub accounts for the most: 34,516 readings (about 2,876 hours) on 122 days, 34,516 of them marked as an outage rather than degraded, most recently on Nov 17, 2026.

ComponentOutageDegradedMaint.DaysLast
Continue Hub34516——122Nov 17, 2026

Counts are five-minute readings of Continue's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

What cascades to Continue

Continue is built on 7 providers. When one of these has an incident, Continue can degrade too.

Incidents and their updates are Continue's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Continue.