- GitHub confirmed the outage at 9:40 AM EDT on August 17, 2026, stating it was investigating reports of performance problems affecting some of its services.
- GitHub is down for some users due to a widespread outage causing errors across the website, API, Actions, Pull Requests, and several other services.
- According to Downdetector, the company is seeing error rates of around 20% across its web experience and API traffic.
- At 12:16 a.m. ET, GitHub posted an update stating: 'We are experiencing high error rates around 20% for web experiences and API traffic.'
- GitHub issued a fix at 12:36 p.m. ET, but mentioned that interruptions may continue as it rolls out.
- The outage appears to be even worse for some repository downloads, with archive downloads and raw repository content downloads experiencing error rates of approximately 50%.
- At 10:31 AM EDT, GitHub confirmed that Copilot was also experiencing degraded availability, expanding the outage to its AI coding services.
- GitHub has not disclosed what caused the outage and states its investigation is ongoing.
- Despite the fix, error rates remain around 20% for web experiences and API traffic, while archive and raw repository content downloads continue to see approximately 50% error rates.
Thousands of users reported issues accessing GitHub's website and app on Monday, with error rates reaching 50% for some services. Downdetector indicated tens of thousands of reports as GitHub confirmed the outage at 9:40 AM EDT, stating it was investigating performance problems affecting various functionalities.13
At 12:16 a.m. ET, GitHub acknowledged high error rates of around 20% for web experiences and API traffic, while repository downloads faced even greater challenges, with approximately 50% error rates for archive and raw content downloads. The outage also impacted GitHub's AI coding services, including Copilot, which experienced degraded availability.47
GitHub issued a fix at 12:36 p.m. ET, but cautioned that interruptions might persist as they rolled out the solution. The company stated, “We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service.” Despite these efforts, error rates remained elevated, and GitHub has not disclosed the cause of the outage, indicating that their investigation is ongoing.589
As users continue to face difficulties, GitHub reassured them that updates would be provided as recovery progresses.
“GitHub is experiencing high error rates, with around 20% for web experiences and API traffic, and approximately 50% for archive and raw repository content downloads. The company has identified the problematic component and is working on restoring full service, with updates expected as recovery continues.”
lifehacker.com
