5 ms·

Mon and Dad (MS) are (generally) pretty solid with uptime. What is happening at GH? Rate of change trying to keep up with new challengers? Over-reliance on AI

Mon and Dad (MS) are (generally) pretty solid with uptime. What is happening at GH? Rate of change trying to keep up with new challengers? Over-reliance on AI? Engineers trying to debug slop?

yashap 1mo ago
Yeah who knows, would be interesting to hear an inside take if any readers here are also GH devs! They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. A glorious one nine of reliability.
- marcprux 1mo ago
  I see two nines in there…
- warmwaffles 1mo ago
  Don't throw shade, there are two nines in that percentage for now. Miles a part though.
  - alamsterdam 1mo ago
    911 has one! :)
- reilly3000 1mo ago
  Yea just try requesting an SLA credit from them. According to THEIR numbers it’s 99.995%. It’s intolerable and I am going to put my full weight behind stripping as much work as we can from GHA as possible, even if leaving GitHub itself is effectively logistically and contractually impossible.
- gitgud 1mo ago
  > They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. I don’t love GitHub, but that number is a little misleading… That’s the intersection uptime of all GitHub services, most of which I (and most users) do not care about; code spaces, copilot, packages etc… When you take out those uptimes, it becomes a lot higher. I’ll admit there seems to be a lot more incidents than usual though…
simoncion 1mo ago
> What is happening at GH? In large part, the move from AWS to Azure. Azure's just bad.
- alamsterdam 1mo ago
  wasn't that years ago? or was that Skype? hahaha
  - simoncion 1mo ago
    AFAIK, the move to Azure is still ongoing. Rumor has it that it was delayed for a very long time after the Github acquisition because Azure was too bad to move Github to. Azure remains too bad to move Github to, but the relevant executives have pretty clearly decided that that's no longer a good reason to delay the move.
- PsylentKnight 1mo ago
  Based on previous posts I've seen about this, IIRC the timing seems to imply that it has more to do with them being hammered with AI slop than it does with the Azure transition. Who really knows though
  - simoncion 1mo ago
    > ...IRC the timing seems to imply that it has more to do with them being hammered with AI slop... It can be both things. I've worked professionally with AWS, Azure, and GCP, and Azure is just really flaky and unreliable. It's easily the worst of the three.

Mon and Dad (MS) are (generally) pretty solid with uptime. What is happening at GH? Rate of change trying to keep up with new challengers? Over-reliance on AI? Engineers trying to debug slop?

yashap 1mo ago

Yeah who knows, would be interesting to hear an inside take if any readers here are also GH devs! They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. A glorious one nine of reliability.

marcprux 1mo ago
I see two nines in there…
warmwaffles 1mo ago
Don't throw shade, there are two nines in that percentage for now. Miles a part though.
- alamsterdam 1mo ago
  911 has one! :)
reilly3000 1mo ago
Yea just try requesting an SLA credit from them. According to THEIR numbers it’s 99.995%. It’s intolerable and I am going to put my full weight behind stripping as much work as we can from GHA as possible, even if leaving GitHub itself is effectively logistically and contractually impossible.
gitgud 1mo ago
> They're at 93.91% uptime over the past 90 days, according to https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/ , and that doesn't even include today's outage yet. I don’t love GitHub, but that number is a little misleading… That’s the intersection uptime of all GitHub services, most of which I (and most users) do not care about; code spaces, copilot, packages etc… When you take out those uptimes, it becomes a lot higher. I’ll admit there seems to be a lot more incidents than usual though…

simoncion 1mo ago

> What is happening at GH? In large part, the move from AWS to Azure. Azure's just bad.

alamsterdam 1mo ago
wasn't that years ago? or was that Skype? hahaha
- simoncion 1mo ago
  AFAIK, the move to Azure is still ongoing. Rumor has it that it was delayed for a very long time after the Github acquisition because Azure was too bad to move Github to. Azure remains too bad to move Github to, but the relevant executives have pretty clearly decided that that's no longer a good reason to delay the move.
PsylentKnight 1mo ago
Based on previous posts I've seen about this, IIRC the timing seems to imply that it has more to do with them being hammered with AI slop than it does with the Azure transition. Who really knows though
- simoncion 1mo ago
  > ...IRC the timing seems to imply that it has more to do with them being hammered with AI slop... It can be both things. I've worked professionally with AWS, Azure, and GCP, and Azure is just really flaky and unreliable. It's easily the worst of the three.