Codacy incident

Issues authenticating with GitHub

Minor Resolved View vendor source →
Started
Mar 11, 2026, 02:39 PM UTC
Resolved
Mar 11, 2026, 02:39 PM UTC
Duration
Detected by Pingoru
Mar 11, 2026, 02:39 PM UTC

Update timeline

  1. resolved Mar 11, 2026, 02:39 PM UTC

    Mar 11, 2026, 15:05 UTC Resolved - Mar 11, 2026, 14:51 UTC Identified - We have identified the likely cause of the authentication issues affecting the GitHub connector as the ongoing GitHub incident. We are seeing intermittent behaviour, with some login attempts succeeding, some failing with “Could not retrieve token to authenticate the account” or “Bad credentials,” and some succeeding on retry. We have also observed that clearing cookies or re-authenticating with GitHub may improve success in some cases. We are continuing to monitor the situation. Mar 11, 2026, 14:39 UTC Investigating - We are investigating an issue affecting authentication through the GitHub connector. Some users may be unable to log in or sign up and may see the message: “Could not retrieve token to authenticate the account.” We are actively working to identify the cause and will provide another update as soon as we have more information. This issue might be related with the ongoing GitHub incident https://www.githubstatus.com/incidents/zy1gjfc6x2z9.

Looking to track Codacy downtime and outages?

Pingoru polls Codacy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Codacy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Codacy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Codacy for free

5 free monitors · No credit card required