Disruption with creation of fine grained personal access tokens

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 44m it lasted.

  Anything that failed between 2026-08-10 18:02 UTC and 2026-08-10 18:46 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 5

1. investigatingAug 10, 2026, 6:02 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. investigatingAug 10, 2026, 6:09 PM UTC

   We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.

   provider

3. monitoringAug 10, 2026, 6:21 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

   provider

4. monitoringAug 10, 2026, 6:22 PM UTC

   We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.

   provider

5. resolvedAug 10, 2026, 6:46 PM UTC

   On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT was created. Creating classic personal access tokens, as well as editing or deleting existing FG PAT were not affected. The cause was a change to how the website loads certain front-end JavaScript that was enabled for all users at 17:15 UTC; the change interacted with an issue in the token creation form's confirmation step that prevented it from running, so the final submission that actually creates the token never completed. Because the page still loaded and the server returned a normal response, the failure produced no error message. GitHub mitigated the incident by disabling the change at 18:21 UTC, at which point token creation recovered immediately, and the incident was resolved at 18:46 UTC. To reduce the chance of recurrence, GitHub is adding monitoring and alerting for anomalies in the FG PAT creation success rate and is removing the issue in the FG PAT creation form that prevented the confirmation step from running. GitHub is also adding automated detection of the issue so other areas of the GitHub front end do not repeat the problem.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.