CodeRabbit Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live CodeRabbit status99.97% uptime history

Every Recorded CodeRabbit Incident

CodeRabbit incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Incident: Reviews might be impacted13 minResolved
Oct 19, 2026Incident: Reviews might be impacted1h 51mResolved
Oct 19, 2026Incident: Reviews might be impacted4 minResolved
Oct 19, 2026Incident: Reviews might be impacted12 minResolved
Oct 19, 2026Incident: Reviews might be impacted6 minResolved
Oct 19, 2026Degraded Performance on Login and Reviews7h 9mResolved
Oct 19, 2026Incident: Reviews might be impacted8 minResolved
Oct 19, 2026Incident: Reviews might be impacted1h 45mResolved
Sep 25, 2026Incident: Reviews might be impacted12 minResolved
Sep 1, 2026Incident: Reviews might be impacted1h 19mResolved
Sep 1, 2026Outage in app, reviews1h 33mResolved
Sep 1, 2026Incident: Reviews might be impacted58 minResolved
Aug 19, 2026PR Triage outage2h 42mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next CodeRabbit incident opens instead, at the point where knowing still changes what you do.

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

How to Read This CodeRabbit Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CodeRabbit acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single CodeRabbit outage in this window ran 7h 9m, against a mean recovery of 1h 24m. If you depend on CodeRabbit in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.