Major impactResolvedDevOps

GitHub outage: Degradation with Webhooks, Pull Requests and Actions

GitHub reported this major-impact incident on its official status page on Jun 25, 2026, 17:50 UTC. It was resolved after 37 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jun 25, 2026, 17:50 UTC
started
Jun 25, 2026, 18:27 UTC
resolved
37 min
duration
Major
impact
  1. resolvedJun 25, 2026, 18:27 UTC

    On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances. The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub outage on Jun 25, 2026: Degradation with Webhooks, Pull Requests and Actions · APIStatus.watch