Is Qodo down?
Last checked 6m agoNo incidents right now.
Qodo is operational right now. Last checked 6m ago; the most recent incident resolved 8d ago.
Real-time Qodo status, recent outages, and incident history: pulled directly from Qodo's official status page at status.qodo.ai every 5 minutes. Pingoru tracks 15 Qodo services and has captured 3 incidents in the last 90 days (99.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Qodo reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Single-tenant Instances
Timeline · 2 updates
- investigating · Oct 14, 2026, 08:40 AM UTC
Status: Investigating Starting around 4:40 AM ET (08:40 UTC), some single-tenant Qodo deployments stopped processing incoming pull request events. Automatic reviews and other PR-triggered actions aren't running for pull requests opened or updated since then. Affected components Single-tenant Instances (Partial outage)
- resolved · Oct 14, 2026, 11:50 AM UTC
Status: Resolved On October 14, between about 4:40 and 7:50 AM ET (08:40–11:50 UTC), some single-tenant Qodo deployments didn't process incoming pull request events. Automatic reviews and other PR-triggered actions didn't run for pull requests opened or updated during that window. Cause and resolution: A deployment change left our event-processing service without its queue settings. We corrected the settings, but the affected services didn't restart automatically to pick them up, so we restarted them manually. Service has been fully operational since 7:50 AM ET. Events received during this window weren't queued and won't be replayed. If a review didn't run during this window, you can trigger it again by commenting /agentic_review on the PR or pushing a new commit. Next steps: We're updating the service so it restarts automatically when its settings change. We apologize for the disruption to your workflow. If you have any questions, reach out to us at [email protected]: mailto:[email protected]. Affected components Single-tenant Instances (Operational)
Latest: Status: Resolved On October 14, between about 4:40 and 7:50 AM ET (08:40–11:50 UTC), some single-tenant Qodo deployments didn't process incoming pull request events. Automatic revi…
-
- GitHubGitLabBitbucketAzure DevOpsGerritLocal code reviewAI ModelsSingle-tenant Instances
Timeline · 3 updates
- identified · Oct 13, 2026, 10:51 AM UTC
Status: Identified Qodo AI reviews are currently degraded. Some reviews may fail to complete or return errors. This affects both multi-tenant and single-tenant environments. The root cause has been identified, and our engineering team is working on a fix. Affected components GitHub (Partial outage) Gerrit (Partial outage) GitLab (Partial outage) Azure DevOps (Partial outage) Bitbucket (Partial outage) AI Models (Full outage) Local code review (Partial outage) Single-tenant Instances (Partial outage)
- monitoring · Oct 13, 2026, 12:03 PM UTC
Status: Monitoring We’ve applied a fix, and AI reviews are working again. Between about 10:50 and 12:00 UTC, AI reviews in multi-tenant and single-tenant environments failed to complete or returned errors. We’re watching the system to make sure it stays stable. If a review failed during that window, please run it again. We’ll post another update once we confirm the issue is fully resolved. Affected components AI Models (Operational) Local code review (Operational) Single-tenant Instances (Operational) GitHub (Operational) Gerrit (Operational) GitLab (Operational) Azure DevOps (Operational) Bitbucket (Operational)
- resolved · Oct 13, 2026, 02:12 PM UTC
Status: Resolved On October 13, between 6:51 and 8:03 AM ET (10:51 - 12:03 UTC), PR reviews and other AI-backed features were unavailable for SaaS customers. Customers using their own model keys (BYOK) were not affected. Cause and resolution: As part of ongoing work to strengthen security on our AI gateway, we applied a configuration change to tighten access controls. The change unintentionally blocked our services’ access to AI models. Our team restored the correct configuration, and service has been fully operational since 8:03 AM ET. No data was lost or exposed. If a review didn’t run during this window, you can trigger it again by commenting /agentic_review on the PR or pushing a new commit. Next steps: We’re adding validation to how these changes are applied and improving our alerting so issues like this are caught immediately. Affected components Bitbucket (Operational) AI Models (Operational) Local code review (Operational) Single-tenant Instances (Operational) GitHub (Operational) Gerrit (Operational) GitLab (Operational) Azure DevOps (Operational)
Latest: Status: Resolved On October 13, between 6:51 and 8:03 AM ET (10:51 - 12:03 UTC), PR reviews and other AI-backed features were unavailable for SaaS customers. Customers using their …
-
Incident record
Since October 2026 · incident.io · 15 components checked every 5 minutesThe longest incident in the last year, Degraded performance for AI reviews on October 13, 2026, ran for 3 hours. 1 maintenance window announced in the same period.
Most affected components, last 12 months
- Single-tenant Instances2
- AI Models1
- Azure DevOps1
- Bitbucket1
- Gerrit1
Latest incidents
- Automatic PR reviews not triggered for some single-tenant customers
Status: Investigating Starting around 4:40 AM ET (08:40 UTC), some single-tenant Qodo deployments stopped processing incoming pull request events. Automatic…
- Degraded performance for AI reviews
Status: Identified Qodo AI reviews are currently degraded. Some reviews may fail to complete or return errors. This affects both multi-tenant and single-tenant…
- Started Oct 14, 2026, 08:40 AM UTC · Resolved Oct 14, 2026, 11:50 AM UTC · 3h 10m
- Degraded performance for AI reviews ResolvedStarted Oct 13, 2026, 10:51 AM UTC · Resolved Oct 13, 2026, 02:12 PM UTC · 3h 21m