[2025-07-29] Incident Thread #167956
Replies: 4 comments
-
UpdateWe are seeing an increase in 429s when retrieving git artifacts from GitHub.com. This is manifesting in many ways, for example, in failed GitHub Actions workflow runs. We have our engineers working on mitigation and we will provide more information as we have it. Thank you for your patience. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe identified and removed unhealthy hosts from our system. This has led to a reduction of 429s and a return to normal operating conditions. We are continuing to monitor recovery and will resolve the incident once we are confident the impact has been mitigated. |
Beta Was this translation helpful? Give feedback.
-
UpdateContinued monitoring is showing that impact has been mitigated and normal service operation has been restored. We are going to resolve the incident at this time. Thank you for your patience as we investigated this problem. |
Beta Was this translation helpful? Give feedback.
-
Incident ResolvedThis incident has been resolved. |
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:
Increase in 429s for Git Operations
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