I have had intermittent issues with winget today. I use UniGetUI for a front-end, and anything tied to Microsoft has failed for me. Judging by the logs, it's mostly retrieving the listing of versions (I assume similar to what 'apt-get update' does, I'm fairly new to using winget for Windows package management).

Also cant do anything right now with the repo's we have in Azure Devops, how lovely...

get vscodium then

"BREAKING: Alaska Airlines' website, app impacted amid Microsoft Azure outage"

https://www.youtube.com/watch?v=YJVkLP57yvM

Pretty much every single Microsoft domain I've tried to access loads for a looooong time before giving me some bare html. I wonder if someone can explain why that's happening.

I am unable to load this article...presumably for related reasons

That specific subdomain has issues with propagation: https://dnschecker.org/#A/answers.microsoft.com (only four resolvers return records)

The root zone and www. do not: https://dnschecker.org/#A/microsoft.com (all resolvers return records)

And querying https://www.microsoft.com/ results in HTTP 200 on the root document, but the page elements return errors (a 504 on the .css/.js documents, a 404 on some fonts, Name Not Resolved on scripts.clarity.ms, Connection Timed Out on wcpstatic.microsoft.com and mem.gfx.ms). That many different kinds of errors is actually kind of impressive.

I'm gonna say this was a networking/routing issue. The CDN stayed up, but everything else non-CDN became unroutable, and different requests traveled through different paths/services, but each eventually hit the bad network path, and that's what created all the different responses. Could also have been a bad deploy or a service stopped running and there's different things trying to access that service in different ways, leading to the weird responses... but that wouldn't explain the failed DNS propagation.

wow, right after AWS suffered a similar thing.

I wonder if this is microsoft "learning" to "prevent" such an issue and instead triggered it...

"One often meets his destiny on the path he takes to avoid it" -- Master Oogway

2027: the year of migrating from your own metal to a managed provider

2028: the year of migrating from a managed provider to the cloud

2029: the year of migrating from the cloud to your own metal in a rack

People keep thinking the solution to their problems is to do something new (that they don't fully understand).

TIL it's called Nirvana Fallacy

I'd predict the year of linux desktop instead.

I've been doing it since 1998 in my bedroom with a dual T1 (and on to real DCs later). While I've had some outages for sure it makes me feel better I am not that divergent in uptime in the long run vs big clouds.

... and DNS caching, and browser file cache, and sessions...

Moving a website quickly is never fun.

That status page is never red. Absolutely useless.

> There are currently no active events. Use Azure Service Health to view other issues that may be impacting your services.

Links to a page on Azure Portal which is down...

They added a message at the same time as your comment:

"We are investigating an issue with the Azure Portal where customers may be experiencing issues accessing the portal. More information will be provided shortly."

All of our Azure workloads are up, but we don't use Azure Front Door. That seems to be the only impacted product, apart from the management portal.

FWIW, all of our databases, VMs, AKS clusters, services, jobs etc - are all working fine. Which services are down for you, maybe we can build a list?

Does their status page depend on something that is down already, so the page just fails static now hence no new updates?

Same playbook for AWS. When they admitted that Dynamo was inaccessible, they failed to provide context that their internal services are heavily dependent on Dynamo

It's only after the fact they are transparent about the impact