Major outageGitHub ・ June 10, 2026

Authentication issues related to API requests

A record of the GitHub incident on June 10, 2026 (UTC): start time, duration and severity, plus current status, what to do, and alternatives.

Started
Jun 10, 2026, 03:20 PM UTC
Resolved
Jun 10, 2026, 04:39 PM UTC
Duration
1h 18m
Impact
Major outage

Other providers down at the same time

2 other incident(s) at different providers overlapped with this one. It may not have been limited to a single service — several providers were degraded at once.

  • AnthropicElevated errors on Claude Haiku 4.5
  • CursorInvestigating service degradation — Cloud Agents

Derived from our own archive of official status pages across 13 providers. Items lasting more than 24 hours and unresolved items are excluded, as they would misrepresent the moment.

How big was this outage?

This outage lasted 78 minutes. Across 58 major incidents recorded for GitHub, the median duration is 95 minutes, making this the 38th longest.

Shorter than a typical outage.

Only incidents recorded as major-or-worse and already resolved are counted.

Current status

GitHub is operating normally now. This incident has been resolved.

See current GitHub status →

What you can do during an outage

Source: GitHub's official status page.

Other GitHub incidents

  1. Grok 4.6 and Grok 4.7 Service IssuesOctober 23, 2026
  2. Disruption with Dependabot AlertsOctober 23, 2026
  3. Delayed Actions status check resultsOctober 23, 2026
  4. Project updates delayedOctober 22, 2026
  5. Incident with Actions ResultsOctober 22, 2026