Qodo

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-14 08:40 UTC

   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 2026-10-14 11:50 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...

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-13 10:51 UTC

   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 2026-10-13 12:03 UTC

   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...

3. resolved 2026-10-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...

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-02-01 11:33 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. identified 2023-02-01 11:37 UTC

   The issue has been identified and a fix is being implemented.

3. investigating 2023-02-01 11:37 UTC

   We are currently investigating this issue.

4. investigating 2023-02-01 11:37 UTC

   We are continuing to investigate this issue.

5. resolved 2023-02-01 11:52 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2023-01-18 11:19 UTC

   Let your users know once a fix is in place, and keep communication clear and precise.

2. identified 2023-01-18 11:25 UTC

   As you continue to work through the incident, update your customers frequently.

3. resolved 2023-01-18 11:29 UTC

   Empathize with those affected and let them know everything is operating as normal.

4. investigating 2023-01-18 11:55 UTC

   When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2023-02-21 08:44 UTC

   The issue has been identified

2. identified 2023-02-21 08:45 UTC

   We are continuing to work on a fix for this issue.

3. identified 2023-02-21 09:06 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2023-02-21 10:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-02-17 05:42 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-02-17 05:43 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-02-14 17:11 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-02-14 17:12 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-02-09 09:35 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-02-09 10:05 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-17 13:12 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-17 13:17 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-07 12:14 UTC

   We are currently investigating this issue.

2. resolved 2023-03-07 12:52 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-06 11:27 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-06 12:03 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-04 08:34 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-04 08:35 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-02 16:27 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-02 16:29 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-04-30 15:01 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-04-30 15:04 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-22 19:01 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-22 19:03 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-22 18:38 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-22 18:43 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-22 17:55 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-22 17:59 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-03-20 22:51 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-03-20 22:55 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-20 11:57 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-08-20 12:20 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-02 05:41 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-08-02 05:42 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-16 07:20 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-07-16 07:21 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-08 08:14 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-07-08 08:14 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-06-28 06:34 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-06-28 06:34 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-18 05:16 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-05-18 05:17 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-20 12:23 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2023-08-20 12:25 UTC

   Thank you for your patience. All Codium services are online.

Excerpts are shortened. Read the full incident on Qodo's status page.