GitHub incident

Authentication issues related to API requests

Critical Resolved View vendor source →

GitHub experienced a critical incident on June 10, 2026 affecting API Requests and Issues, lasting 1h 18m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2026, 03:20 PM UTC
Resolved
Jun 10, 2026, 04:39 PM UTC
Duration
1h 18m
Detected by Pingoru
Jun 10, 2026, 03:20 PM UTC

Affected components

API RequestsIssues

Update timeline

  1. investigating Jun 10, 2026, 03:20 PM UTC

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

  2. investigating Jun 10, 2026, 03:23 PM UTC

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

  3. investigating Jun 10, 2026, 03:27 PM UTC

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

  4. investigating Jun 10, 2026, 03:27 PM UTC

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

  5. investigating Jun 10, 2026, 03:46 PM UTC

    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.

  6. investigating Jun 10, 2026, 03:46 PM UTC

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

  7. investigating Jun 10, 2026, 04:21 PM UTC

    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.

  8. investigating Jun 10, 2026, 04:36 PM UTC

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

  9. monitoring Jun 10, 2026, 04:37 PM UTC

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

  10. resolved Jun 10, 2026, 04:39 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.