GitHub Outage Disrupts Core Services Globally for Users

GitHub experienced a widespread outage on July 28, 2025, affecting millions of developers and organizations reliant on its services.

The incident, which impacted API requests, issue tracking, and pull requests, highlighted the vulnerabilities in cloud-based collaboration tools essential for software development worldwide.

The outage began around 10:40 PM UTC on July 28, when GitHub’s status page reported degraded performance in these core features.

Users across the globe, from individual coders to enterprise teams, faced difficulties accessing repositories, submitting code changes, and managing project issues.

This came at a critical time for many, as GitHub powers everything from open-source projects to proprietary software pipelines for tech giants.

According to the incident timeline, GitHub’s engineering team initiated an investigation immediately after reports surfaced. By 10:42 PM UTC, they confirmed the issues and began probing potential causes.

Early updates indicated degraded performance in some services, with the team identifying networking issues as a likely cause.

As the night progressed into July 29, the situation escalated. An update at 11:18 PM UTC noted continued degradation, and by midnight, efforts focused on mitigating what appeared to be infrastructure-related issues.

The impact was notable but contained. At its peak, approximately 4% of requests to the affected services resulted in errors, causing intermittent failures rather than a complete shutdown. This partial disruption still led to widespread frustration, with social media buzzing about delayed deployments and halted workflows.

Developers in regions like North America, Europe, and Asia reported slowdowns during peak hours, underscoring GitHub’s role as a backbone for global tech ecosystems.

For instance, teams using GitHub for continuous integration and deployment (CI/CD) pipelines experienced bottlenecks, potentially delaying product releases and updates.

GitHub’s response was swift. By 12:51 AM UTC on July 29, the team provided an update on ongoing mitigation, emphasizing that only a small fraction of traffic was affected.

Progress accelerated shortly after: at 1:52 AM UTC, a fix was deployed, and monitoring showed recovery across all impacted areas. Issues tracking normalized by 2:03 AM UTC, followed by pull requests at 2:05 AM UTC. Full resolution was declared at 2:06 AM UTC, with GitHub promising a detailed root cause analysis soon.

This event echoes previous GitHub incidents, reminding users of the platform’s occasional hiccups despite its robust infrastructure.

As a Microsoft-owned service since 2018, GitHub serves over 100 million repositories and supports collaborative coding for enterprises like Google and NASA. The outage, lasting roughly three and a half hours, affected users globally but was resolved before major business hours in many time zones.

In the aftermath, experts suggest diversifying tools or implementing local backups to mitigate such risks. GitHub has not yet released the root cause, but the incident report indicates networking issues were central.

Users are advised to check regional status pages such as eu.githubstatus.com for Europe, au.githubstatus.com for Australia, and us.githubstatus.com for the US for localized updates. No further incidents were reported as of July 29, 2025, allowing the platform to return to normal operations.

Experience faster, more accurate phishing detection and enhanced protection for your business with real-time sandbox analysis-> Try ANY.RUN now