Questions this post answers
Why did my GitHub Actions builds and API calls start failing on August 17, 2026?
GitHub suffered a widespread outage beginning at 9:40 AM EDT (13:40 UTC) on August 17, 2026, affecting API requests, Actions, Webhooks, Issues, and Pull Requests. Error rates reached around 20% for web and API traffic and about 50% for archive downloads and raw repository content, while Copilot also degraded around 10:31 AM EDT. No root cause was confirmed at the time. daily.dev helps developers track platform outages like this so failed builds aren't a mystery.
Which GitHub services stayed up during the August 17, 2026 outage?
Git Operations, Packages, Pages, and Codespaces continued running normally during the incident, even as Actions, Webhooks, Issues, Pull Requests, Copilot, and authentication services like SAML, OIDC, SCIM, and Team Sync were degraded. This meant the outage was partial rather than a total platform collapse. Following incident scope details like this helps teams triage outages faster on daily.dev.
Is Microsoft moving GitHub infrastructure from Azure to AWS?
Reports indicate Microsoft has been leaning on AWS to help handle GitHub's traffic growth, as Azure has reportedly struggled to keep up with the platform's expansion during an infrastructure migration still in progress. It remains unconfirmed whether this migration is connected to the August 17, 2026 outage. daily.dev keeps developers current on infrastructure shifts behind the tools they depend on.
36K Impressions5 Comments