3 ms·
33 minutes from impact to status page for a complete outage is a joke.
by xnorswap 1y ago
33 minutes from impact to status page for a complete outage is a joke.
- neya 1y agoIn Microsoft's defense, Azure has always been a complete joke. It's extremely developer unfriendly, buggy and overpriced.
- michaelt 1y agoIf you call that defending microsoft, I'd hate to see what attacking them looks like :)
- dude250711 1y agoSave it for when they stick Copilot into Azure portal.
- antonvdi 1y agoThey're already doing that.
- alias_neo 1y agoHa, you haven't used it recently have you? Copilot is already there, and it can't do a single useful thing. Me: "How do I connect [X] to [Y] using [Z]?" Copilot: "Please select the AKS cluster you'd like to delete"
- GuestFAUniverse 1y agoPerfect answer /s
- nflekkhnnn 1y agoActually one of the inventors of k8s was the project lead for copilot in the azure portal, and deployed it over a year ago.
- dijit 1y agoNot to put too fine a point on it, but if I have a dark passenger in my tech life it is almost entirely caused by what Microsoft wants to inflict on humanity - and more importantly; how successful they are at doing it.
- amelius 1y agoIn commenter's defense, their comment makes no sense.
- madjam002 1y agoMy favourite was the Azure CTO complaining that Git was unintuitive, clunky and difficult to use
- macintux 1y agoIsn’t it?
- Hilift 1y agoIronically, the GitHub Desktop Windows app is quite nice.
- dspillett 1y agoYes. But the point is compared to Azure in places the statement was very much the pot commenting on the kettles sooty arse. And git makes no particular pretence to be particularly friendly, just that it does a particular job efficiently.
- lawgimenez 1y agoSounds like he’s describing Windows phone.
- ac2u 1y agoFeel like I have to defend windows phone here, I liked it! Although I swore off the platform after the hardware I bought wasn’t eligible for the windows phone 8 upgrade even though the hardware was less than two years old. They punished early adopters
- lawgimenez 1y agoYeah Windows Phone's first releases were decent. I have developed apps for Windows actually using Window's UWP framework but there weren't enough users on their platform sadly.
- sfn42 1y agoI've only used Azure, to me it seems fine ish. Some things are rather overcomplicated and it's far from perfect but I assumed the other providers were similarly complicated and imperfect. Can't say I've experienced many bugs in there either. It definitely is overpriced but I assume they all are?
- sofixa 1y ago> In Microsoft's defense, Azure has always been a complete joke. It's extremely developer unfriendly, buggy and overpriced. Don't forget extremely insecure. There is a quarterly critical cross-tenant CVE with trivial exploitation for them, and it has been like that for years.
- hinkley 1y agoGiven how much time I spent on my first real multi-tenant project, dealing with the consequences of architecture decisions meant to prevent these sorts of issues, I can see clearly the temptation to avoid dealing with them. But what we do when things are easy is not who we are. That's a fiction. It's how we show up when we are in the shit that matters. It's discipline that tells you to voluntarily go into all of the multi-tenant mitigations instead of waiting for your boss to notice and move the goalposts you should have moved on your own.
- rk06 1y agoHmm, isn't that the same argument we use in defense of windows and ms teams?
- sbergot 1y agoand for a while the status was "there might be issues on azure portal".
- ambentzen 1y agoThere might have been, but they didn't know because they couldn't access it. Could have been something totally unrelated.
- infaloda 1y agoMore importantly `15:45 UTC on 29 October 2025 – Customer impact began. 16:04 UTC on 29 October 2025 – Investigation commenced following monitoring alerts being triggered. ` A 19-minute delay in alert is a joke.
- Xss3 1y agoThat does not say it took 19 minutes for alerts to appear. Following could mean any amount of time.
- hinkley 1y agoIt's 19 minutes until active engagement by staff. And planned rolling restarts can trigger alerts if you don't set thresholds of time instead of just thresholds of count. It would be nice though if alert systems made it easy to wire up CD to turn down sensitivity during observed actions. Sort of like how the immune system turns down a bit while you're eating.
- hinkley 1y ago10 minutes to alert, to avoid flapping false positives. 10 minute response window for first responders. Or, 5 minute window before failing over to backup alerts, and 4 minutes to wake up, have coffee, and open the appropriate windows.
- tremon 1y agoI'd like to think that a company the size of Microsoft can afford to have incident response teams in enough time zones to cover basic operations without relying on night shifts.
- hinkley 1y agoThat’s some very carefully chosen phrasing. I think if you really wanted to do on call right to avoid gaps you’d want no more than 6 hours on primary per day per shift, and you want six, not four, shifts per day. So you’re only alone for four hours in the middle of your shift and have plenty of time to hand off.
- imglorp 1y agoThat's about how long it took to bubble up three levels of management and then go past the PR and legal teams for approvals.
- skeezyjefferson 1y ago[flagged]
- thayne 1y agoUnfortunately,that is also typical. I've seen it take longer than that for AWS to update their status page. The reason is probably because changes to the status page require executive approval, because false positives could lead to bad publicity, and potentially having to reimburse customers for failing to meet SLAs.
- ape4 1y agoPerhaps they could set the time to when it really started after executive approval.
- HeavyStorm 1y agoI've been on bridges where people _forgot_ to send comms for dozens of minutes. Too many inexperienced people around these days.
- schainks 1y agoAWS either is “on it” or you they will say something somewhere between 60-90 minutes after impact. We should be lucky MSFT is so consistent! Hug ops to the Azure team, since management is shredding up talent over there.
- campbel 1y agoAs a technologist, you should always avoid MS. Even if they have a best-in-class solution for some domain, they will use that to leverage you into their absolute worst-in-class ecosystem.
- hinkley 1y agoI see Amazon using a subset of the same sorts of obfuscations that Microsoft was infamous for. They just chopped off the crusts so it's less obvious that it's the same shit sandwich.