Outage recap · Qodo

Qodo outage — October 14, 2026

On October 14, 2026, Qodo had 2 reported incidents on Qodo's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Degraded performance for AI reviews

critical
Started
Oct 14, 9:26 AM EDT
Resolved
Oct 13, 10:12 AM EDT
Duration
—

Qodo's updates (3)

  1. identified · Oct 13, 6:51 AM EDT

    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.

  2. monitoring · Oct 13, 8:03 AM EDT

    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.

  3. resolved · Oct 13, 10:12 AM EDT

    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.

What our checks recorded

We have no checks recorded from Qodo's start time to its resolution.

Updates are Qodo's own words from its status page (status: resolved); we never add an inferred cause.

Automatic PR reviews not triggered for some single-tenant customers

major
Started
Oct 14, 9:51 AM EDT
Resolved
Oct 14, 7:50 AM EDT
Duration
—

Qodo's updates (2)

  1. investigating · Oct 14, 4:40 AM EDT

    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.

  2. resolved · Oct 14, 7:50 AM EDT

    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](mailto:support@qodo.ai).

What our checks recorded

We have no checks recorded from Qodo's start time to its resolution.

Updates are Qodo's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Qodo. This recap summarizes incidents published on Qodo's official status page.