14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others!
reply[1] https://www.theverge.com/tech/865689/microsoft-claude-code-a...
An interesting thing I notice now is that people do not like companies that only post about outages if half the world have them ... and also not companies that also post about "minor issues", e.g.:
reply> During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes.
That's for sure not perfect, but there was also a 95% chance that if you have re-run the job, it will run and not fail to start. Another one is about notificatiosn being late. I'm sure all others do have similar issues people notice, but nobody writes about them. So a simple "to many incidents" does bot make the stats bad - only an unstable service the service.
Dude, that's just a reason to scream at the clouds... Literally...
replyAt this point they are probably going to crash their status system. "No one ever expected more than 50 incidents in a month!"
replyYou know what I think would reverse the trend? More vibe coding!
replyI know you are joking but I'm sure that there is at least one director or VP inside GitHub pushing a new salvation project that must use AI to solve all the problems, when actually the most likely reason is engineers are drawing in tech debt.
reply> I'm sure that there is at least one director or VP inside GitHub pushing a new salvation project that must use AI to solve all the problems
replyGitHub is under Microsoft’s CoreAI division, so that’s a pretty sure bet.
https://www.geekwire.com/2025/github-will-join-microsofts-co...
Upper management in Microsoft has been bragging about their high percentage of AI generated code lately - and in the meantime we've had several disastrous Windows 11 updates with the potential to brick your machine and a slew of outages at github. I'm sure it might be something else but it's clear part of their current technical approach is utterly broken.
replyCoPilot has done more for Linux than anyone expected. I switched. I'm switching my elderly parents away next before they fall victim.
replySays everything... https://www.youtube.com/shorts/Dj_f2ANBfas
replyUtterly broken - perhaps, but apparently that's not exclusive with being highly profitable, so why should they care?
replyWhen I first typed up my comment I said "their current business approach" and then corrected it to technical since - yea, in the short term it probably isn't hurting their pocket books too much. The issue is that it seems like a lot more folks are seriously considering switching off Windows - we'll see if this actually is the year of the linux desktop (it never seems to be in the end) but it certainly seems to be souring their brand reputation in a major way.
replyFor the time being. Does anyone want Windows 11 for real?
replyThe inertia is not permanent.
Cause it's finally the year of Linux on desktop.
replyIt’s not a joke.
This is funny because it is true.
replyBetter to replace management by AI.
replyComputers can produce spreadsheets even better and they can warm the air around you even faster.
I mean, the strengths of LLMs were always a much better match for the management than for technical work:
reply* writing endless reports and executive summaries
* pretending to know things that they don't
* not complaining if you present their ideas as yours
* sycophancy and fawning behavior towards superiors
deleted
replyPlus they don't take stock options!
replyHonestly AI management would probably be better. "You're a competent manager, you're not allowed to break or circumvent workers right laws, you must comply with our CSR and HR policies, provide realistic estimates and deliver stable and reliable products to our customers." Then just watch half the tech sector break down, due to a lack of resources, or watch as profit is just cut in half.
replyAll the cool kids move fast and break things. Why not the same for core infrastructure providers? Let's replace our engineers with markdown files named after them.
replyThis kind of thing never happened before LLMs!
replyNo, the reason it's happening is because they must be vibe coding! :P
replyThat's not good enough. You need SKILLS!
replyI'm happy that they're being transparent about it. There's no good way to take downtime, but at least they don't try to cover it up. We can adjust and they'll make it better. I'm sure a retro is on its way it's been quite the bumpy month.
replyI think this will continue to happen until they finish migrating to Azure
replyThe main root cause of the incident on their actions was actually due to Azure: https://www.githubstatus.com/incidents/xwn6hjps36ty points to https://azure.status.microsoft/en-us/status/history/?trackin...
replyHaven't they been shown the front door?
replywut
replyProbably referring to the fact that they no longer are independent, do not have a CEO and are a division of a division within Microsoft.
replyI was sort of hoping this would be a year-to-date visualization similar to Github profile contribution graphs...
replySomeone should make a timeline chart from that, lol.
replyHere it is. It looks like they are down to a single 9 at this point across all services:
replyCan you add a line graph with incidents per month? Would be useful to see if the number of incidents are going up or down over time.
replyI threw together <https://mkantor.github.io/github-incident-timeline/>. It's by day rather than month, and only shows the last 50 incidents since that's all their API returns.
replyHaha, that would be awesome!
replyLight work for an LLM
replyBut not Copilot.
replyCopilot is shown as having policy issues in the latest reports. Oh my, the irony. Satya is like "look ma, our stock is dropping...", Gee I wonder why Mr!!
reply