GitHub incident
Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions
GitHub experienced a minor incident on June 5, 2026, lasting 5h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 05, 2026, 05:20 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Jun 05, 2026, 05:25 PM UTC
Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
- investigating Jun 05, 2026, 06:04 PM UTC
During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.
- monitoring Jun 05, 2026, 06:05 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Jun 05, 2026, 06:43 PM UTC
We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
- monitoring Jun 05, 2026, 08:34 PM UTC
Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should see them succeed.
- monitoring Jun 05, 2026, 10:21 PM UTC
Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues.
- resolved Jun 05, 2026, 10:21 PM UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.