Microsoft says the outage affecting GitHub's API, Actions, Pull Requests, and other services has been mitigated, three hours after it first confirmed the outage
BleepingComputerMayank Parmar
Context & Ripple Effects
The earlier coverage established that GitHub's disruption was widespread across its website, API, Actions and Pull Requests; this update closes the immediate incident cycle with Microsoft's mitigation notice. It also adds GitHub to a record of Microsoft service interruptions that has previously spanned collaboration, cloud and productivity products.
First-order effects
Developers and teams using GitHub's API, Actions and Pull Requests move from an active availability incident to service-stability monitoring as Microsoft reports mitigation.
Second-order effects
Projects whose builds, integrations or code-review workflows were held up by the outage can resume, while engineering teams may need to reconcile work delayed during the incident.
If cross-service disruptions persist, developers will increasingly treat code-hosting availability and automation continuity as linked operational risks rather than separate tool issues.
The trend: Microsoft's expanding service footprint is concentrating more workplace and development workflows behind shared availability dependencies.
Netlify is now a git host. Some data points from million repos created via Drop and Agent Runs with Netlify Source: git clone GitHub: p50 385ms, p95 1510ms Netlify: p50 282ms, p95 693ms Full CI setup GitHub: p95 3.3s Netlify: p95 1.5s Read more in Dana's Post:👇👇👇
Damn, we are hitting levels of GitHub dysfunction I haven't really seen before. Forget GitHub actions not working, now the web app can't even retrieve the commits!
This is the “313 Team,” the Iranian hacktivist group that DDoS-ed BlueSky yesterday and a bunch of social media sites earlier this year [embedded post]