DEV TOOLS Signal 618 2 feeds carried it
GitHub reports degraded performance across Webhooks, Actions, API, Pull Requests, and Issues
↗
Illustration only Photo by Hunter Haley on Unsplash
Developers may experience delayed webhook deliveries, slower CI runs, and failed API calls due to the ongoing degradation of multiple GitHub services.
CI/CD pipelines that rely on GitHub Actions or webhooks can face delays or failures, affecting release automation. Teams should monitor the GitHub status page and consider fallback mechanisms for critical integrations.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Webhooks, Actions, and API Requests are each reporting degraded performance as of the August 17, 2026 updates.
Pull Requests and Issues show an approximate 20% error rate across numerous experiences.
GitHub continues to investigate and provides regional status pages for au, eu, jp, and us domains.
THE READ
What the cluster adds up to.
On August 17, 2026, GitHub posted a series of status updates indicating degraded performance for several core services. The first update at 13:41 UTC noted API Requests degradation, followed by Actions at 13:42 UTC and Webhooks at 13:44 UTC. Later updates added Pull Requests and Issues to the list of affected experiences.
The degradation manifests as increased latency for webhook deliveries and slower execution of GitHub Actions workflows. Additionally, the status page reports an approximate 20% error rate across Pull Requests, Issues, and other experiences. These effects can disrupt automated pipelines that depend on timely webhook notifications or reliable CI runs.
GitHub states that investigations are ongoing and that updates will be posted as they become available. The status page shows a timeline of updates from the initial investigation at 13:40 UTC through the latest at 13:58 UTC. No resolution has been declared yet, and the team continues to monitor the situation.
Regional status pages are available for Australia, EU, Japan, and the US, allowing teams to check performance in their specific geography. Historical uptime data shows that services such as Actions had 99.43% uptime over the past 90 days, while Webhooks and API Requests have maintained near-100% uptime prior to the incident. This context helps engineers assess whether the current degradation is an anomaly or part of a broader trend.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER