Issues logging in with GitHub

Update timeline

1. investigating Oct 24, 2026, 08:22 AM UTC

   We’re investigating an issue where users can’t log in with GitHub, and operations involving GitHub organizations may fail.

2. identified Oct 24, 2026, 09:20 AM UTC

   We have identified the source of the issue and are rolling out a fix.

3. monitoring Oct 24, 2026, 09:30 AM UTC

   We have rolled out the fix and are seeing that logins and API requests are now working as expected. We are monitoring.

4. investigating Oct 24, 2026, 09:42 AM UTC

   We have identified further problems and are investigating.

5. investigating Oct 24, 2026, 10:01 AM UTC

   We are still investigating the root cause of failures to login.

6. identified Oct 24, 2026, 11:22 AM UTC

   We are still working to restore reliable GitHub logins and API access. Some users may be unable to log in with GitHub, and some API requests and operations involving GitHub organizations may fail intermittently. Starting at approximately 21:45 WEST on Oct 23, after an unannounced change on GitHub's side, responses from GitHub's sign-in service became larger than a size limit in our platform. This prevented our platform from completing GitHub logins and from renewing the GitHub access that many API requests rely on. We rolled out a fix for this at 10:30 WEST on Oct 24, raising that limit with extra headroom. However, many GitHub authorizations could not be renewed while the issue was ongoing and were left in an inconsistent state. Restoring them has caused GitHub to repeatedly throttle requests from our platform, which is still preventing some logins and causing API requests to fail authentication. We are working on changes to reduce these requests and resolve the throttling.

7. identified Oct 24, 2026, 11:54 AM UTC

   We continue working to resolve the GitHub throttling affecting logins and API requests. Some GitHub authorizations could not be renewed during the incident and will need to be restored by logging in again: if you are affected, please log out of Codacy, log in again at app.codacy.com using "Log in with GitHub", and approve the authorization if GitHub asks for it. This may particularly affect service accounts used only through the Codacy API, for example in CI pipelines and scripts, since they don't log in regularly. Their requests may fail with 404 Not Found errors (such as "Could not find repository") or authentication errors even though the repository exists and the account still has access. To restore them, log in once to the Codacy web app as that service account's GitHub user and authorize Codacy when prompted. Existing Codacy API tokens remain valid and don't need to be changed. If problems persist after logging in again, please contact our support team.

8. identified Oct 24, 2026, 11:55 AM UTC

   Identified

9. monitoring Oct 24, 2026, 12:34 PM UTC

   We have rolled out mitigation measures to prevent GitHub throttling. We are monitoring the situation closely. Some GitHub authorizations could not be renewed during the incident and must be restored by logging in again through the Codacy web app: if you are still affected, please log out of Codacy, log in again at app.codacy.com using "Log in with GitHub", and approve the authorization if GitHub asks for it. This is especially important for service accounts used only through the Codacy API, for example in CI pipelines and scripts, whose requests may keep failing with 404 Not Found errors (such as "Could not find repository") or authentication errors until someone logs in once to the Codacy web app as that service account's GitHub user and authorizes Codacy. Existing Codacy API tokens remain valid and don't need to be changed. If problems persist after logging in again, please contact our support team.