Authentication issues related to API requests

Summary

Authentication issues related to API requests

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.

• Started

  Jun 10, 2026 · 3:20 PM

• Resolved

  Jun 10, 2026 · 4:39 PM

• Duration

  1h 18m

• Severity

  Critical

• ◐

  Investigating

  Jun 10 · 3:20 PM GitHub

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

• ◐

  Investigating

  Jun 10 · 3:23 PM GitHub

  API Requests is experiencing degraded availability. We are continuing to investigate.

• ◐

  Investigating

  Jun 10 · 3:27 PM GitHub

  Issues is experiencing degraded performance. We are continuing to investigate.

• ◐

  Investigating

  Jun 10 · 3:27 PM GitHub

  We are investigating issues related to sporadic authentication failures impacting approximately 15% of API traffic. We will continue to investigate and provide updates.

• ◐

  Investigating

  Jun 10 · 3:46 PM GitHub

  We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Further updates will be provided as we work to mitigate.

• ◐

  Investigating

  Jun 10 · 3:46 PM GitHub

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

• ◐

  Investigating

  Jun 10 · 4:21 PM GitHub

  We continue to investigate issues related to sporadic authentication failures, impacting approximately 15% of API traffic. Erroneous 401 responses are causing app integrations to trigger authentication flows. We have identified a problematic component in our infrastructure and are working to mitigate.

• ◐

  Investigating

  Jun 10 · 4:36 PM GitHub

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

• ◉

  Monitoring

  Jun 10 · 4:37 PM GitHub

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

• ✓

  Resolved

  Jun 10 · 4:39 PM GitHub

  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.