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% 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.
- Service disruption for Qodo cloud customersOct 29, 2026 → Oct 29, 2026 · resolved
- Automatic PR reviews not triggered for some single-tenant customersOct 14, 2026 → Oct 14, 2026 · resolved
- Degraded performance for AI reviewsOct 14, 2026 → Oct 13, 2026 · resolved
- Degraded performance for AI reviewsOct 13, 2026 · ongoing · resolved
- Elevated API ErrorsJul 30, 2026 → Feb 1, 2023 · resolved
- This is an example incidentJul 30, 2026 → Jan 18, 2023 · resolved
- Elevated API ErrorsJul 30, 2026 → Feb 17, 2023 · resolved
- Elevated API ErrorsJul 30, 2026 → Feb 9, 2023 · resolved
- Services are downJul 30, 2026 → Feb 21, 2023 · resolved
- Elevated API ErrorsJul 30, 2026 → Feb 14, 2023 · resolved
- Elevated error rateJul 30, 2026 → Mar 7, 2023 · resolved
- Elevated API ErrorsJul 30, 2026 → Mar 4, 2023 · resolved
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.
| Component | Outage | Degraded | Maint. | Days | Last |
|---|---|---|---|---|---|
| AI Models | — | 12 | — | 1 | Oct 29, 2026 |
| Azure DevOps | — | 12 | — | 1 | Oct 29, 2026 |
| Bitbucket | — | 12 | — | 1 | Oct 29, 2026 |
| Codebase Wisdom | — | 12 | — | 1 | Oct 29, 2026 |
| Gerrit | — | 12 | — | 1 | Oct 29, 2026 |
| GitHub | — | 12 | — | 1 | Oct 29, 2026 |
| GitLab | — | 12 | — | 1 | Oct 29, 2026 |
| Local code review | — | 12 | — | 1 | Oct 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
- Oct 29, 2026Service disruption for Qodo cloud customerscritical2 h 3 min4 updates
- Oct 14, 2026Automatic PR reviews not triggered for some single-tenant customersmajor—2 updates
- Oct 14, 2026Degraded performance for AI reviewscritical—3 updates
- Oct 13, 2026Degraded performance for AI reviewsmajorend not published
July 2026 · 22
- Jul 30, 2026Elevated API Errorsmajor—5 updates
- Jul 30, 2026This is an example incidentnone—4 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Services are downnone—4 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated error ratemajor—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
- Jul 30, 2026Elevated API Errorsnone—2 updates
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.