Skip to main content
CodeRabbit logo

Is CodeRabbit Down?

No — CodeRabbit is up

Reachable from all 8 checked regions

Average response time: 217ms

Last checked · checks run every 6 hours

Official status page: https://status.coderabbit.ai

CodeRabbit uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
260ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

15-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: no data
Sep 27: no data
Sep 28: no data
Sep 29: 100.00% uptime, 16 checks
Sep 30: 100.00% uptime, 29 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
356ms
DNS 275ms TCP 1ms TLS 20ms TTFB 342ms
fra
238ms
DNS 169ms TCP 1ms TLS 8ms TTFB 227ms
gru
96ms
DNS 29ms TCP 2ms TLS 6ms TTFB 86ms
iad
184ms
DNS 100ms TCP 1ms TLS 7ms TTFB 156ms
jnb
434ms
DNS 249ms TCP 1ms TLS 63ms TTFB 377ms
lax
236ms
DNS 122ms TCP 1ms TLS 24ms TTFB 215ms
lhr
94ms
DNS 25ms TCP 2ms TLS 11ms TTFB 84ms
nrt
99ms
DNS 14ms TCP 2ms TLS 9ms TTFB 89ms

What CodeRabbit does

CodeRabbit is an AI code review service. Installed on a GitHub, GitLab, Azure DevOps or Bitbucket organization, it reads each new pull request and posts a summary, a walkthrough and line-by-line review comments, then updates its review as new commits are pushed. It also offers IDE and CLI reviews. It depends on the git host's API and webhooks and on model providers such as OpenAI and Anthropic.

What an outage looks like

The usual sign is a pull request that gets no CodeRabbit summary or review comments, or a CodeRabbit review status that never finishes. Past incidents were posted as Reviews might be impacted, an outage in the app and reviews, a PR Triage outage, and CodeRabbit not able to authenticate to GitHub, when PRs were not reviewed at all. A GitHub API outage can stop reviews even while coderabbit.ai loads normally.

What to do about it

Check status.coderabbit.ai, which lists Website, App, Reviews and Docs plus third-party rows for OpenAI, Anthropic, GitHub, GitLab, Bitbucket, Jira, Slack and Google Cloud. If a git host row is red, nothing on your side needs fixing. CodeRabbit can publish its review status for required checks, so a stalled review may hold merges. Once reviews recover, comment @coderabbitai review on a skipped PR, or @coderabbitai full review for a fresh pass.

Is it down for everyone, or just you?

If this page says CodeRabbit is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
GitLab
GitLab
Bitbucket
Bitbucket
Graphite
Graphite

CodeRabbit outage FAQ

Is CodeRabbit down for everyone or just me?
Look at status.coderabbit.ai first: an incident there, usually on the Reviews row, means it is not your setup. If everything is green and only one repository gets no reviews, check whether someone commented @coderabbitai pause on the pull request, which halts automatic reviews until @coderabbitai resume. CodeRabbit's in-app chat reaches its support team, and a support form covers users who are locked out.
Does a GitHub outage affect CodeRabbit?
Yes, heavily. On July 16, 2026 CodeRabbit could not authenticate to GitHub for about 68 minutes and PRs were not reviewed. Its postmortem said GitHub did not seem to count that incident as downtime, but because of how CodeRabbit works, 35% API downtime for GitHub meant 100% downtime for CodeRabbit. The status page tracks GitHub webhooks, pull requests, API requests and git operations as separate rows.
Will CodeRabbit review my pull request after an outage?
It reviews again when new commits are pushed, but a pull request opened during the outage may need a nudge. Comment @coderabbitai review to run an incremental review of changes since the last one, or @coderabbitai full review to review the whole pull request from scratch, ignoring earlier comments. Both commands come from CodeRabbit's documentation and work while automatic reviews are paused.
Can an OpenAI or Anthropic outage stop CodeRabbit reviews?
It can, which is why CodeRabbit's status page lists the OpenAI API and api.anthropic.com as third-party components next to its own. On September 1, 2026 an outage in the app and reviews lasted about 90 minutes, and CodeRabbit's update said downstream third-party services had implemented a fix. Check those rows when reviews stop but the website works.
How long do CodeRabbit outages usually last?
Most posted incidents are short. Review incidents on September 5 and September 25, 2026 were resolved in 2 and 10 minutes after a fix was deployed. Longer ones exist: the September 1, 2026 app and reviews outage ran about 90 minutes, and a PR Triage outage on August 19, 2026 lasted about 2 hours 40 minutes. Timelines are on status.coderabbit.ai.

How we measure this

  • We request CodeRabbit's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where CodeRabbit publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when CodeRabbit goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required