GitHub experience various partial-outages/degradations
by bhouston on 2/2/2026, 9:28:16 PM
https://www.githubstatus.com?todayis=2026-02-02
Comments
by: llama052
Looks like Azure as a platform just killed the ability for VM scale operations, due to a change on a storage account ACL that hosted VM extensions. Wow... We noticed when github actions went down, then our self hosted runners because we can't scale anymore.<p>Information<p>Active - Virtual Machines and dependent services - Service management issues in multiple regions<p>Impact statement: As early as 19:46 UTC on 2 February 2026, we are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs) across multiple regions. These issues are also causing impact to services with dependencies on these service management operations - including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, Azure Load Testing, and GitHub. For details on the latter, please see <a href="https://www.githubstatus.com" rel="nofollow">https://www.githubstatus.com</a>.<p>Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working on mitigation, including updating configuration to restore relevant access permissions. We have applied this update in one region so far, and are assessing the extent to which this mitigates customer issues. Our next update will be provided by 22:30 UTC, approximately 60 minutes from now.<p><a href="https://azure.status.microsoft/en-us/status" rel="nofollow">https://azure.status.microsoft/en-us/status</a>
2/2/2026, 10:02:47 PM
by: guywithabike
It's notable that they blame "our upstream provider" when it's quite literally the same company. I can't imagine GitHub engineers are very happy about the forced migration to Azure.
2/2/2026, 10:59:10 PM
by: fbnszb
As an isolated event, this is not great, but when you see the stagnation (if not downwards trajectory) of GitHub as a whole, it‘s even worse in my opinion.<p>edit: Before someone says something. I do understand that the underlying issue is some issue with Azure.
2/2/2026, 10:11:58 PM
by: maddmann
This is why I come to hacker news. Sanity check on why my jobs are failing.
2/2/2026, 10:34:29 PM
by: fishgoesblub
Getting the monthly GitHub outage out of the way early, good work.
2/2/2026, 11:33:22 PM
by: falloutx
50% of code written by AI, now let the AI handle this outage.
2/2/2026, 10:25:34 PM
by: booi
Copilot being down probably increased code quality
2/2/2026, 10:07:21 PM
by: focusgroup0
Will paid users be credited for the wasted Actions minutes?
2/2/2026, 11:54:26 PM
by: levkk
This happens routinely every other Monday or so.
2/2/2026, 11:05:23 PM
by: suriya-ganesh
It is always a config problem. somewhere somplace in the mess of permissioning issues.
2/2/2026, 10:49:47 PM
by: re-thc
Jobs get stuck. Minutes are being consumed. The problem isn't just it being unavailable.
2/2/2026, 11:04:03 PM
by: jmclnx
With linkedin down, I wonder if this is an azure thing ? IIRC github is being moved to azure, maybe the azure piece was partially enabled ?
2/2/2026, 9:36:20 PM
by: rvz
Tay.ai and Zoe AI Agents probably running infra operations at GitHub and still arguing about how to deploy to production without hallucinating a config file and deploying a broken fix to address the issue.<p>Since there is no GitHub CEO, (Satya is not bothered anymore) and human employees not looking, Tay and Zoe are at the helm ruining GitHub with their broken AI generated fixes.
2/2/2026, 10:53:31 PM
by: ChrisArchitect
Some more earlier: <a href="https://news.ycombinator.com/item?id=46860544">https://news.ycombinator.com/item?id=46860544</a>
2/2/2026, 9:54:59 PM