Qodo logo

Is Qodo Down?

Developer ToolsLive status, outages, and incident history

No. Qodo is up right now.

Every monitored Qodo system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Qodo breaks

Qodo is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Qodo status page
How we know: the official Qodo status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Qodo Status Summary

As of 12:40 UTC on 9 November 2026, Qodo is operational. PulsAPI checked Qodo's official status page and found 15 of 15 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.80% uptime for Qodo, counting degraded performance as up. The latest incident, "Service disruption for Qodo cloud customers", was on Oct 29, 2026 and lasted 3h 46m.

Cite as: PulsAPI, “Qodo status”, checked 9 November 2026, 12:40 UTC. https://www.pulsapi.com/services/qodo

Qodo Component Status

The main Qodo systems on this page. All 15 are operational right now.

15operational
AI Models
Operational
Azure DevOps
Operational
Bitbucket
Operational

12 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Codebase Wisdom, Docs & Help Center, Gerrit, GitHub, GitLab, Local code review, MCP server, Qodo Portal, qodo.ai website, Rules, Sign-in & SSO, Single-tenant Instances.

See all of them free

Component statuses may change independently during partial outages.

Recent Qodo Outages & Incidents

Incident history from the official Qodo status page, including resolution updates.

Service disruption for Qodo cloud customersResolved Oct 29, 2026 · 3h 46mResolved

The issue affecting Qodo cloud services has been resolved. Impact occurred from 09:44 to 12:33 UTC. --- [2026-10-29T12:44:52Z] (monitoring) All Qodo cloud services have been restored, and we are monitoring to make sure everything stays stable. Pull requests opened or updated between 09:44 and 12:33 UTC may not have been reviewed. To get a review, comment /agentic_review on the pull request. --- [2026-10-29T11:48:52Z] (identified) > Most Qodo cloud services have been restored, and we are monitoring the recovery. Some customers may still experience disruption while we finish restoring service. We will provide an update as soon as possible. --- [2026-10-29T11:58:31Z] (investigating) We are experiencing a service disruption affecting all Qodo services for cloud customers. Qodo services are currently down. We are working to restore service and will provide an update as soon as possible.

Automatic PR reviews not triggered for some single-tenant customersResolved Oct 14, 2026Resolved

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.

Automatic PR reviews not triggered for some single-tenant customersResolved Oct 14, 2026 · 3h 10mResolved

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). --- [2026-10-14T13:51:40Z] (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.

Qodo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Qodo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.94% average · 2 days with incidentsNov 9

Going further back: Qodo uptime by month and every recorded Qodo outage.

Live Qodo Outage Reports

Problems reported by engineers using Qodo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Qodo problems reported yet.

Something wrong with Qodo on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Qodo

Qodo publishes a public status page at status.qodo.ai covering 2 components, including API and qodo.ai web site. PulsAPI tracks Qodo outages, degraded performance and incident history in real time, alongside the rest of your developer tooling stack.

Over the past 30 days, PulsAPI has measured Qodo uptime at 99.80%. Response times, incident history, and SLA tracking for Qodo are available on the PulsAPI dashboard.

Qodo Status FAQ

Is Qodo down right now?

The verdict at the top of this page comes from the latest poll of the official Qodo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Qodo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Qodo recovers.

How do I check Qodo uptime history?

PulsAPI tracks Qodo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.80%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Qodo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Qodo outages?

PulsAPI reads the official Qodo status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Qodo components?

Yes. PulsAPI monitors 15 individual Qodo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Qodo goes down?

Yes. Create a free account and subscribe to Qodo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Qodo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Qodo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Qodo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Qodo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Qodo with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services