Rewindex

CompaniesCodeRabbitIncidents

CodeRabbit: Incident: CodeRabbit not able to authenticate to GitHub

unknownStatus: postmortemStarted Resolved (18 h)4 updatesstatus.coderabbit.ai (opens in new tab)
Part of an outage event

GitHub outage, Jul 16, 2026 · 14 vendors, 16 incidents

CodeRabbit’s incident blames GitHub as the cause. (hop 1, posted +1 h 38 min vs GitHub’s own post)

“…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…”

Swipe sideways to see the whole diagram.

GitHubposted 21:05 UTCWithin an hour1 vendorSentry1 to 4 hours later7 vendors, 5 blamed GitHubRender, CodeRabbit, CircleCI, Bitrise +3CodeRabbit (this incident)posted +1 h 38 min
GitHubposted 21:05 UTCWithin an hour1 vendorSentry1 to 4 hours later7 vendors, 5 blamed GitHubRender, CodeRabbit, CircleCI,Bitrise +3CodeRabbit (this incident)posted +1 h 38 min
CodeRabbit is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["GitHub<br/>posted 21:05 UTC"]:::root
  h1["Within an hour<br/>1 vendor<br/>Sentry"]:::names
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 5 blamed GitHub<br/>Render, CodeRabbit, CircleCI, Bitrise +3"]:::blames
  root --> h4
  me["CodeRabbit (this incident)<br/>posted +1 h 38 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: ReviewsWebsite

Timeline of updates

  1. investigating

    CodeRabbit is not able to authenticate to GitHub. PRs are not getting reviewed. DownDetector says that there is a GitHub outage currently. <https://downdetector.com/status/github/>.

  2. identified

    We are continuing to work on a fix for this incident..

  3. resolved

    We have detected GitHub authentications working again. This incident we are considering as resolved..

  4. postmortem

    This is the GitHub incident that comprised the sole cause of this incident - <https://www.githubstatus.com/incidents/gxycch3076xk> . They do not seem to have counted it as downtime, but because of the nature of our system 35% API downtime for GitHub is 100% downtime for us..

Impact, status and times are the vendor’s own, as last archived. View on status.coderabbit.ai (opens in new tab).

CodeRabbit profileRecent CodeRabbit incidentsMarkdownJSON