User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with CodeRabbit.
Correction: On Nov 10, 2026 we retracted an incident report for CodeRabbit published in error on Nov 9, 2026. No outage occurred. Read the retraction →
Estimated fix: Not enough CodeRabbit history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Reachable from all 4 regions we check from.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 9 min ago. Last stored result reached it in 212 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 02 | 0 | 0.0 | 175 ms | 0 |
| Mon 04 | 0 | 0.0 | 67 ms | 0 |
| Mon 06 | 0 | 0.0 | 236 ms | 0 |
| Mon 08 | 0 | 0.0 | 129 ms | 0 |
| Mon 10 | 0 | 0.0 | 320 ms | 0 |
| Mon 12 | 0 | 0.0 | 62 ms | 0 |
| Mon 14 | 0 | 0.0 | 74 ms | 0 |
| Mon 17 | 0 | 0.0 | 160 ms | 0 |
| Mon 19 | 0 | 0.0 | 198 ms | 0 |
| Mon 21 | 0 | 0.0 | 287 ms | 0 |
| Mon 23 | 0 | 0.0 | 115 ms | 0 |
| Tue 01 | 0 | 0.0 | 208 ms | 0 |
| Tue 03 | 0 | 0.0 | 93 ms | 0 |
| Tue 05 | 0 | 0.0 | 72 ms | 0 |
| Tue 07 | 0 | 0.0 | 222 ms | 0 |
| Tue 09 | 0 | 0.0 | 74 ms | 0 |
| Tue 11 | 0 | 0.0 | 97 ms | 0 |
| Tue 14 | 0 | 0.0 | 155 ms | 0 |
| Tue 16 | 0 | 0.0 | 203 ms | 0 |
| Tue 18 | 0 | 0.0 | 82 ms | 0 |
| Tue 20 | 0 | 0.0 | 94 ms | 0 |
| Tue 23 | 0 | 0.0 | 106 ms | 0 |
| Wed 01 | 0 | 0.0 | 113 ms | 0 |
| Wed 03 | 0 | 0.0 | 225 ms | 0 |
| Wed 05 | 0 | 0.0 | 132 ms | 0 |
| Wed 08 | 0 | 0.0 | 88 ms | 0 |
| Wed 10 | 0 | 0.0 | 117 ms | 0 |
| Wed 12 | 0 | 0.0 | 152 ms | 0 |
| Wed 14 | 0 | 0.0 | 69 ms | 0 |
| Wed 16 | 0 | 0.0 | 79 ms | 0 |
| Wed 18 | 0 | 0.0 | 164 ms | 0 |
| Wed 21 | 0 | 0.0 | 454 ms | 0 |
| Wed 23 | 0 | 0.0 | 122 ms | 0 |
| Thu 01 | 0 | 0.0 | 140 ms | 0 |
| Thu 03 | 0 | 0.0 | 167 ms | 0 |
| Thu 05 | 0 | 0.0 | 107 ms | 0 |
| Thu 07 | 0 | 0.0 | 299 ms | 0 |
| Thu 09 | 0 | 0.0 | 109 ms | 0 |
| Thu 11 | 0 | 0.0 | 103 ms | 0 |
| Thu 13 | 0 | 0.0 | 104 ms | 0 |
| Thu 15 | 0 | 0.0 | 185 ms | 0 |
| Thu 17 | 0 | 0.0 | 88 ms | 0 |
| Thu 19 | 0 | 0.0 | 160 ms | 0 |
| Thu 22 | 0 | 0.0 | 298 ms | 0 |
| Fri 00 | 0 | 0.0 | 97 ms | 0 |
| Fri 02 | 0 | 0.0 | 89 ms | 0 |
| Fri 05 | 0 | 0.0 | 141 ms | 0 |
| Fri 07 | 0 | 0.0 | 212 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for CodeRabbit yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when CodeRabbit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CodeRabbit alerts to Slack, Discord or a webhook — free.
CodeRabbit, at coderabbit.ai, is one of the AI services we monitor. Ship more software, faster, with code you trust. Independent AI code review, PR triage, change explanations, and continuous security monitoring.
CodeRabbit publishes an official status page at status.coderabbit.ai; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 152 ms average, 78–299 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public CodeRabbit incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
152 ms on average over the last 24 hours (78–299 ms). Latest regional checks: US East 178 ms, US West 198 ms, Europe 86 ms, Asia-Pacific 280 ms.
Yes, at https://status.coderabbit.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report CodeRabbit here at once, the problem is on CodeRabbit's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with CodeRabbit. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.