4 ms·

The worst part of all this is that GitHub's CTO and VP of Engineering sent out the usual "here's what we'll do to fix things" letter to their larger customers a

The worst part of all this is that GitHub's CTO and VP of Engineering sent out the usual "here's what we'll do to fix things" letter to their larger customers and, without exaggeration, it boiled down to: 1) "Here's a bunch of stuff we already did!" which... clearly isn't working, and 2) "We're continuing our Azure migration." also clearly not working. So needless to say, if you depend on GitHub for critical business operations, you need to start thinking about what a world without GitHub looks like for your business and start working your way toward that. I know my confidence in GitHub's engineering leadership is at rock bottom.

Eji1700 6mo ago
I could sorta see a situation where the reality is "we're in the middle of a miserable transition and it'll clean up when we're done" but I don't think anyone has confidence that's all it is at this point.
- everforward 6mo ago
  Even that doesn’t really make sense to me, unless they’ve done it in a way where everything has to move at once. Everywhere I’ve worked, if a migration is causing this much downtime then you kill the migration or slow it down. If every change has a 10% chance of bringing the site down, you only do a change every week or two until you can work out the kinks.
  - acedTrex 6mo ago
    I mean, they are seemingly breaking every week or two so that might be what they are doing.
  - shrikant 6mo ago
    ...or you keep fighting forward with the migration, because if it's seen as a failure then some pretty big heads will have to roll...
    - ahartmetz 6mo ago
      Reminds me of the bank for my business where a larger bank with terrible IT bought a smaller bank with great IT - guess which systems they standardized on? Online banking is still much worse than before and the web interface still says "will be migrated by end of 2023" for some parts. Many customers just left and complaints were widely reported in the media. I probably should leave, too.
- suriya-ganesh 6mo ago
  also it should be noted that LinkedIn had a 5 year plan of migrating everything to azure but abandoned it after a year.
packetlost 6mo ago
I second this. I'm done.
sysworld 6mo ago
ooooh, they're migrating to Azure, now everything makes sense.
- cyanydeez 6mo ago
  they're not just migrating to Azure, they're vibrating to Azure!
- spondyl 6mo ago
  Here are some relevant excerpts from an October 2025 article[1]: > In a message to GitHub’s staff, CTO Vladimir Fedorov notes that GitHub is constrained on capacity in its Virginia data center. “It’s existential for us to keep up with the demands of AI and Copilot, which are changing how people use GitHub,” he writes. > The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months. “This means we have 18 months to execute (with a 6 month buffer),” Fedorov’s memo says. He acknowledges that since any migration of this scope will have to run in parallel on both the new and old infrastructure for at least six months, the team realistically needs to get this work done in the next 12 months. If you consider that six month parallel window to have started from the time of the October memo (written presumably at the start of October), then that puts us currently or past the point where they would have cut off their old DC and defaulted to Azure only. Whether plans or timelines changed, I have no idea of course but the above does make for a convenient timeline that would explain the recent instability. Of course, it could also just be symptomatic of increased AI usage generally and the same problems might have surfaced at a software level regardless of whether they were in a DC or on Azure. Putting that nuance aside, personally I like the idea that Azure is simply a giant pile of shit operated by a corporation with no taste. [1]: https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/ https://thenewstack.io/github-will-prioritize-migrating-to-a...
  - Barrin92 6mo ago
    >It’s existential for us to keep up with the demands of AI and Copilot if by chance the CTO reads this, as a user of GitHub I would find it really existential if GitHub continues functioning as a reliable hub for git workflows (hence the name), and I have the strong suspicion nobody except for the shareholders gives a lick about copilot or 'AI' if it makes the core service the site was designed for unusable
ryukoposting 6mo ago
Is "migrating to Azure" the new "migrating to SAP?"
- trvz 6mo ago
  That’s not for to … SAP.
justinko 6mo ago
There’s plenty of alternatives, but people continue to stay. Therefore, it’s not as bad as you think it is.
AustinDev 6mo ago
Vibe coding and it's consequences. "The evidence is clear: Either you embrace AI, or get out of this career." -Github CEO "Sooner than later, 80% of the code is going to be written by Copilot. And that doesn’t mean the developer is going to be replaced." -Github CEO
zombot 6mo ago
The worst part is that users still stay and take the abuse.

Eji1700 6mo ago

I could sorta see a situation where the reality is "we're in the middle of a miserable transition and it'll clean up when we're done" but I don't think anyone has confidence that's all it is at this point.

everforward 6mo ago
Even that doesn’t really make sense to me, unless they’ve done it in a way where everything has to move at once. Everywhere I’ve worked, if a migration is causing this much downtime then you kill the migration or slow it down. If every change has a 10% chance of bringing the site down, you only do a change every week or two until you can work out the kinks.
- acedTrex 6mo ago
  I mean, they are seemingly breaking every week or two so that might be what they are doing.
- shrikant 6mo ago
  ...or you keep fighting forward with the migration, because if it's seen as a failure then some pretty big heads will have to roll...
  - ahartmetz 6mo ago
    Reminds me of the bank for my business where a larger bank with terrible IT bought a smaller bank with great IT - guess which systems they standardized on? Online banking is still much worse than before and the web interface still says "will be migrated by end of 2023" for some parts. Many customers just left and complaints were widely reported in the media. I probably should leave, too.
suriya-ganesh 6mo ago
also it should be noted that LinkedIn had a 5 year plan of migrating everything to azure but abandoned it after a year.

packetlost 6mo ago

I second this. I'm done.

sysworld 6mo ago

ooooh, they're migrating to Azure, now everything makes sense.

cyanydeez 6mo ago
they're not just migrating to Azure, they're vibrating to Azure!
spondyl 6mo ago
Here are some relevant excerpts from an October 2025 article[1]: > In a message to GitHub’s staff, CTO Vladimir Fedorov notes that GitHub is constrained on capacity in its Virginia data center. “It’s existential for us to keep up with the demands of AI and Copilot, which are changing how people use GitHub,” he writes. > The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months. “This means we have 18 months to execute (with a 6 month buffer),” Fedorov’s memo says. He acknowledges that since any migration of this scope will have to run in parallel on both the new and old infrastructure for at least six months, the team realistically needs to get this work done in the next 12 months. If you consider that six month parallel window to have started from the time of the October memo (written presumably at the start of October), then that puts us currently or past the point where they would have cut off their old DC and defaulted to Azure only. Whether plans or timelines changed, I have no idea of course but the above does make for a convenient timeline that would explain the recent instability. Of course, it could also just be symptomatic of increased AI usage generally and the same problems might have surfaced at a software level regardless of whether they were in a DC or on Azure. Putting that nuance aside, personally I like the idea that Azure is simply a giant pile of shit operated by a corporation with no taste. [1]: https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/ https://thenewstack.io/github-will-prioritize-migrating-to-a...
- Barrin92 6mo ago
  >It’s existential for us to keep up with the demands of AI and Copilot if by chance the CTO reads this, as a user of GitHub I would find it really existential if GitHub continues functioning as a reliable hub for git workflows (hence the name), and I have the strong suspicion nobody except for the shareholders gives a lick about copilot or 'AI' if it makes the core service the site was designed for unusable

ryukoposting 6mo ago

Is "migrating to Azure" the new "migrating to SAP?"

trvz 6mo ago
That’s not for to … SAP.

justinko 6mo ago

There’s plenty of alternatives, but people continue to stay. Therefore, it’s not as bad as you think it is.

AustinDev 6mo ago

Vibe coding and it's consequences. "The evidence is clear: Either you embrace AI, or get out of this career." -Github CEO "Sooner than later, 80% of the code is going to be written by Copilot. And that doesn’t mean the developer is going to be replaced." -Github CEO

zombot 6mo ago

The worst part is that users still stay and take the abuse.