GitHub Outage Hits Users Globally, Core Services Unavailable

GitHub experienced a significant global outage on July 28-29, 2025, disrupting core services used by millions of developers worldwide.

The incident, which lasted approximately eight hours, affected API requests, Issues, and Pull Requests functionality before being fully resolved early Tuesday morning.

The outage began around 22:40 UTC on July 28, when GitHub’s engineering team started investigating reports of degraded performance across multiple services.

Initial reports indicated that users were experiencing difficulties accessing essential development tools, including the platform’s issue tracking system and pull request functionality that are critical for collaborative software development.

“We are investigating reports of degraded performance for API Requests, Issues and Pull Requests,” GitHub announced in their first status update.

The timing of the outage proved particularly disruptive for development teams across different time zones, with many users unable to merge code changes or track project issues during peak working hours.

As the incident progressed, GitHub’s technical team identified networking issues as the root cause of the service degradation.

By 23:18 UTC, the company confirmed that “some GitHub services are experiencing degraded performance” while their team worked to determine appropriate mitigation strategies.

The situation persisted through the early morning hours, with GitHub providing regular updates to concerned users.

At 00:51 UTC on July 29, the company reported that “approximately 4% of requests to impacted services continue to error,” indicating that while some progress had been made, significant issues remained.

The breakthrough came around 01:52 UTC when GitHub’s engineering team deployed a mitigation strategy. “Team is deploying a mitigation for this incident.

We will update again once we have verified the fix,” the company announced, providing hope to frustrated users worldwide.

Recovery began systematically, with Issues functionality restored at 02:03 UTC, followed by Pull Requests at 02:05 UTC. The complete resolution was announced at 02:06 UTC, marking the end of the eight-hour ordeal.

“This incident has been resolved. Thank you for your patience and understanding as we addressed this issue,” GitHub stated in their final update.

The company promised to share a detailed root cause analysis once available, a standard practice for major service disruptions.

The outage highlighted the critical dependency of modern software development on cloud-based platforms like GitHub.

With over 100 million users relying on the service for version control and collaboration, any disruption significantly impacts global software development workflows.

While GitHub’s status page currently shows no ongoing incidents, the recent outage serves as a reminder of the importance of robust infrastructure and incident response procedures for platforms that serve as essential development infrastructure for organizations worldwide.

Get Free Ultimate SOC Requirements Checklist Before you build, buy, or switch your SOC for 2025 - Download Now