Qodo outage history

We hold 26 Qodo incidents from Qodo's status page, the newest from Oct 29, 2026. 25 of the 26 listed carry Qodo's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 20d 2h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
100%
0 incidents · no downtime
2015 checks
Operational · 30d
99.81%
1 incident · ≈1h 20m degraded
8638 checks
Operational · since Jun 22, 2026
99.93%
26 incidents · ≈1h 30m degraded
41377 checks

% of our checks that found Qodo 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
Past incidents

How Qodo fails

Since Aug 1, 2026, Qodo's status page has marked 14 Qodo components as impaired, across 157 of our five-minute readings. AI Models accounts for the most: 12 readings (about 1.0 hours) on 1 day, most recently on Oct 29, 2026. Next is Azure DevOps, with 12 readings on 1 day. We hold 26 Qodo incidents from Qodo's status page, the earliest from Jul 30, 2026.

ComponentOutageDegradedMaint.DaysLast
AI Models—12—1Oct 29, 2026
Azure DevOps—12—1Oct 29, 2026
Bitbucket—12—1Oct 29, 2026
Codebase Wisdom—12—1Oct 29, 2026
Gerrit—12—1Oct 29, 2026
GitHub—12—1Oct 29, 2026
GitLab—12—1Oct 29, 2026
Local code review—12—1Oct 29, 2026

Incidents by month: Jul 2026: 22 · Oct 2026: 4

Counts are five-minute readings of Qodo'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.

Every recorded incident

October 2026 · 4

July 2026 · 22

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