## GitHub.com Incident — August 17, 2026 ### What Happened GitHub experienced a **major multi-service outage** on August 17, 2026, affecting several core GitHub.com features simultaneously. The incident was first reported at **13:40 UTC** and was still ongoing as of the latest update at **14:04 UTC**. ### Timeline of Updates (from the official [GitHub Status page](https://www.githubstatus.com/incidents/zkxwbgr0cnmx)) | Time (UTC) | Status | |---|---| | **13:40** | Investigating — reports of impacted performance for some GitHub services | | **13:41** | **API Requests** — degraded performance | | **13:42** | **Actions** — degraded performance | | **13:44** | **Webhooks** — degraded performance | | **13:45** | ~20% error rate across numerous experiences including Pull Requests, Issues, and others | | **13:46** | **Issues** — degraded performance | | **13:58** | **Pull Requests** — degraded performance | | **14:04** | ~20% error rate for web experiences and API traffic; **~50% error rate** for archive downloads and raw repository content downloads | ### Affected Components - **API Requests** - **Actions** - **Webhooks** - **Issues** - **Pull Requests** ### Why It Matters This is a **broad, multi-component outage** hitting the core of GitHub's developer workflow — not just one isolated service. The **~50% error rate on archive downloads and raw repository content** is particularly severe, as these are fundamental operations for cloning, downloading, and distributing code. The **~20% error rate across web experiences and API traffic** means a significant portion of developer requests were failing across the board. This incident comes on the heels of a **10-hour GitHub Actions outage on August 6, 2026**, which GitHub itself called "unacceptable in both its impact and particularity of its duration" in their [July 2026 availability report](https://github.blog/news-insights/company-news/github-availability-report-july-2026/). GitHub acknowledged that "availability continues to be our top priority" but that they "have fallen short of our commitments." This new incident raises further concerns about GitHub's reliability, especially given that [Statusfield reports](https://statusfield.com/is-down/github) GitHub has had **22 incidents this month** and **95.4% availability over the last 30 days**. ### Sources - **[GitHub Status — Incident with GitHub.com](https://www.githubstatus.com/incidents/zkxwbgr0cnmx)** — Official incident timeline and updates - **[Statusfield — Is GitHub Down?](https://statusfield.com/is-down/github)** — Third-party monitoring confirming the outage and affected components - **[PANews coverage](https://panews.io/articles/01a00ffd-4dbd-7009-bde2-f76fa17702f6)** — Independent reporting on the incident - **[GitHub July 2026 Availability Report](https://github.blog/news-insights/company-news/github-availability-report-july-2026/)** — Context on GitHub's recent reliability challenges **Status as of 14:04 UTC:** Incident still **investigating** — no root cause identified and no estimated recovery time provided.