Re:GitHub experience various partial-outages/degradations
by tbrownaw on Monday February 02, 2026 @11:30PM
(#46866519)
> It means that any service designed to survive a control plane outage must statically allocate its compute resources and have enough slack that it never relies on auto scaling. True for AWS/GCP/Azure.
That sounds oddly similar to owning hardware.
Re:GitHub experience various partial-outages/degradations
by ragall on Tuesday February 03, 2026 @12:06AM
(#46866754)
In a way. It means that you can get new capacity most often, but the transition windows where a service gets resized (or mutated in general) has to be minimised and carefully controlled by ops.
Re:GitHub experience various partial-outages/degradations
by everfrustrated on Monday February 02, 2026 @11:50PM
(#46866652)
This outage talks about what appears to be a VM control plane failure (it mentions stop not working) across multiple regions.
AWS has never had this type of outage in 20 years. Yet Azure constantly had them.
This is a total failure of engineering and has nothing to do with capacity. Azure is a joke of a cloud.
Re:GitHub experience various partial-outages/degradations
by mirashii on Tuesday February 03, 2026 @12:02AM
(#46866733)
AWS had an outage that blocked all EC2 operations just a few months ago: https://aws.amazon.com/message/101925/
Re:GitHub experience various partial-outages/degradations
by everfrustrated on Tuesday February 03, 2026 @01:11AM
(#46867170)
This was the largest AWS outage in a long long time and was still constrained to a single AWS region.
Which is my point.
The same fault on Azure would be a global (all-regions) fault.
Re:GitHub experience various partial-outages/degradations
by jamesfinlayson on Tuesday February 03, 2026 @07:28PM
(#46879582)
Yeah I remember one maybe four years ago? Existing workloads were fine but I had to go and tell my marketing department to not do anything until it was sorted because auto-scaling was busted.
It means that any service designed to survive a control plane outage must statically allocate its compute resources and have enough slack that it never relies on auto scaling. True for AWS/GCP/Azure.