Qodo Incident History

Unknown

codium.ai ↗2 components

checked Oct 22, 2026 9:35 AM UTC · Qodo's official status page

We don't have a current reading for Qodo.

Qodo is currently being monitored.

All components operational

Be the first to know

Statusfield watches Qodo alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Qodo incident history

2 reports published by Qodo in the last 30 days

When Qodo breaks, it is typically resolved in 2h 5m — median across 1 resolved incidents over 30 days.

October 14, 2026

Automatic PR reviews not triggered for some single-tenant customers

Last update Oct 14, 2026 · 13:56 UTC

resolvedOct 14 · 08:30 UTC
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 support@qodo.ai.

Reported by Qodo on their status page.

October 13, 2026

Degraded performance for AI reviews

Last update Oct 13, 2026 · 14:12 UTC

resolvedOct 13 · 14:12 UTC
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. We apologize for the disruption to your workflow. If you have any questions, reach out to us at support@qodo.ai.

Reported by Qodo on their status page.