- Status page says
- Operational since Oct 19
- Last 90 days
- 13 incidents
- Rewrites caught
- None so far
- Next deprecation
- None announced
Select a day to jump to its incidents below.
How CodeRabbit reports incidents
Compared with the 152 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.
Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors
- First posted only after it was over
- 0% 0 of the 25 incidents we have in full detail
The first update already said resolved. Typical vendor: 6%.
CodeRabbit: lower than most vendors.
- Time to resolve
- 17 min median; 9 in 10 within 2 h 22 min
From the vendor’s own start and resolve times, over the 130 days of history we have. Typical vendor: 2 h.
CodeRabbit: lower than most vendors.
- Major or critical incidents
- 0.0 a month 0 in the 130 days of history we have
Impact as the vendor labels it. Typical vendor: 1.2 a month.
CodeRabbit: lower than most vendors.
- Rewrites caught
- None so far
Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.
Dependencies
What CodeRabbit relies on and who relies on CodeRabbit, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.
CodeRabbit depends on
| Provider | Evidence | Signal |
|---|---|---|
| GitHub | blamed in 1 incident; together in 1 outage event “…Incident: CodeRabbit not able to authenticate to GitHub CodeRabbit is not able to authenticate to GitHub. PRs are not getting reviewed. DownDetector says that there is a GitHub outage currently. <http…” incident | Likely |
Outage events: Google Cloud us-central1, Sep 1 (timing), GitHub, Jul 16.
Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.
Changes and edits
Incidents CodeRabbit rewrote or removed, and notable changes to the pages we watch.
Struck in red is what CodeRabbit removed. Blue is what they added.
No notable changes yet. We compare every snapshot of CodeRabbit’s status page (taken every 10 minutes) and its 1 tracked pages; 2 ordinary incident revisions were seen.
Pricing and pages we watch
| Page | Versions | Last changed | Last checked | History |
|---|---|---|---|---|
| Privacy policy (opens in new tab) | 1 | No changes yet |
Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
The Weekly Rewind: one short weekly email on what changed at CodeRabbit and the other vendors we track, including silent edits. Subscribe (opens in new tab)
Incidents
25 incidents since Jun 12. Maintenance is left out.
TodayMonday, October 19Mon, Oct 19
7 incidents
- unknown, 1 h 50 minIncident
- unknown, 4 minIncident
- unknown, 11 minIncident
- unknown, 5 minIncident
- unknown, 7 h 8 minIncident
- unknown, 7 minIncident
- unknown, 1 h 43 minIncident
Friday, September 25
1 incident
- unknown, 11 minIncident
Saturday, September 5
1 incident
- unknown, 2 minIncident
Tuesday, September 1
3 incidents
- unknown, 1 h 16 minIncident
- unknown, 1 h 30 minIncident
- unknown, 55 minIncident
Wednesday, August 19
1 incident
- unknown, 2 h 39 minIncident
Thursday, July 16
1 incident
- unknown, 18 hIncident
Tuesday, July 14
1 incident
- unknown, 18 minIncident
Thursday, June 18
2 incidents
- unknown, 3 minIncident
- unknown, 15 minIncident
Wednesday, June 17
3 incidents
- unknown, 9 minIncident
- unknown, 1 h 32 minIncident
- unknown, 1 h 56 minIncident
Tuesday, June 16
2 incidents
- unknown, 38 minIncident
- unknown, 14 minIncident
Monday, June 15
2 incidents
- unknown, 10 minIncident
- unknown, 17 minIncident
Friday, June 12
1 incident
- unknown, 11 minIncident