[2025-05-15] Incident Thread #159337
Replies: 7 comments
-
UpdateWe are investigating fine grained PAT creation failures. We will continue to keep users updated on progress towards mitigation. Existing FGP's are unaffected. |
Beta Was this translation helpful? Give feedback.
-
UpdateWhile we have found a possible cause, we have no update on mitigation steps at this stage. We will continue to keep users updated. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe are exploring the best path forward, but no new update at this stage. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe have identified the cause, and have a working fix. We will continue to update users. |
Beta Was this translation helpful? Give feedback.
-
UpdateThe issue preventing users from creating Personal Access Tokens (PATs) has been resolved. The root cause was identified and a change was reverted to restore functionality. PAT generation is now working as expected. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
Beta Was this translation helpful? Give feedback.
-
Incident SummaryOn May 15, 2025, between 00:08 AM UTC and 10:21 AM UTC, customers were unable to create fine-grained Personal Access Tokens (PATs) on github.com. This incident was triggered by a recent code change to our front end that unintentionally affected the way certain pages loaded and prevented the PAT creation process from completing. We mitigated the incident by reverting the problematic change. To reduce the likelihood of similar issues in the future, we are improving our monitoring for page load anomalies and PAT creation failures and improving our safe deployment practices. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
❗ An incident has been declared:
Disruption with some GitHub services
Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.
Beta Was this translation helpful? Give feedback.
All reactions