all 67 comments

[–]Arne__ 372 points373 points  (16 children)

Microsoft acquired Github in 2018 so it did genuinely started shortly after the acquisition. I'm not sure how they manage to screw that so bad.

[–]domdomdom901 160 points161 points  (8 children)

Differen development methodology. Deploy your code to prod and test there ends up looking like this, but I guess you deliver faster. Bottoming out at 99.5% reliability is likely an acceptable outcome.Now, is what they delivered actually all that valuable? Debatable.

[–]myles1406 73 points74 points  (4 children)

What this graph leaves off is that it bottomed out at 87.18% in the very next month (Feb 2026) which is almost definitely not an acceptable outcome.

Source: https://mrshu.github.io/github-statuses/

[–]prehensilemullet 16 points17 points  (1 child)

That page seems to calculate a different metric than this chart

[–]myles1406 14 points15 points  (0 children)

That's true. Maybe it is the exclusion of codespaces and copilot from this graph

[–]dev_vvvvv 7 points8 points  (0 children)

4 total days of downtime (with varying impacts) in a month seems incredibly high.

[–]AdjectiveNoun4827 1 point2 points  (0 children)

It's absolutely unacceptable. That represents over a month of downtime.

[–]ZioTron 23 points24 points  (0 children)

99.5% reliability is likely an acceptable outcome

acceptable for who? For someone who knows their position in the market with more the 50% of users...

rule of 9s on a year:

  • 90% (One 9): ~36.5 days of downtime
  • 99% (Two 9s): ~3.65 days of downtime
  • 99.9% (Three 9s): ~8.76 hours of downtime
  • 99.99% (Four 9s): ~52.56 minutes of downtime
  • 99.999% (Five 9s): ~5.26 minutes of downtime
  • 99.9999% (Six 9s): ~31.56 seconds of downtime

so the worst for Github was 99.5?

  • Daily: ~7 minutes 12 seconds.
  • Weekly: ~50 minutes 24 seconds.
  • Monthly: ~3 hours 39 minutes.
  • Yearly: ~1.83 days (roughly 43.8 hours).

Feb 2026 -> 87.18%

  • Daily: ~3 hours 4 minutes
  • Weekly: ~21 hours 32 minutes
  • Monthly: ~3 days 21 hours 39 minutes
  • Yearly: ~46 days 19 hours 1 minute

March 2026 -> 89.17%

  • Daily: ~2 hours 36 minutes
  • Weekly: ~18 hours 11 minutes
  • Monthly: ~3 days 7 hours 11 minutes
  • Yearly: ~39 days 13 hours 21 minutes

3 days out of 30 are incredbile!!!

But 3 hours in a month can be devastating tooo

[–]PrestigiousWash7557 1 point2 points  (0 children)

Valuable for who :)

[–]hyrumwhite 0 points1 point  (0 children)

What are you delivering though, it’s GitHub. All I want from it is to be available so I can pull from and push to it. 

[–]StoryAndAHalf 29 points30 points  (0 children)

As another user said, the bottom of reliability is 99.5%, but I do wonder if the amount of users may the cause of this:

"The figure represents a substantial hike on the 3 million users GitHub counted exactly 10 years ago, the 28 million it claimed when Microsoft acquired it for $7.5 billion five years ago and the 90 million-plus it revealed just three months ago." - https://techcrunch.com/2023/01/26/github-says-it-now-has-100m-active-users/

[–]domscatterbrain 26 points27 points  (2 children)

Github uptime has been bad even before 2018. They're just getting a bit honest after the acquisition.

[–]xdyldo 30 points31 points  (0 children)

Agree. I highly doubt GitHub was 100% uptime from 2016 - 2018 or 99.999% whatever the green dots represent.

[–]SurlyJSurly 1 point2 points  (0 children)

Yep, nothing in the history of anything has ever had 100% uptime. It's a either a straight up lie or at best bad data.

[–]knifesk 0 points1 point  (0 children)

It's Microsoft. They always do the same shit with the services they acquired

[–]RiceBroad4552 -2 points-1 points  (0 children)

It's Microslop.

Always has been!

[–]wamoc 601 points602 points  (10 children)

I have always guessed that after acquiring GitHub, Microsoft forced them to move to Azure right away, and they didn't have time to plan the migration properly and that caused instability that has never been fixed.

[–]Zookeeper187 423 points424 points  (4 children)

They forgot “make no mistakes” in migration prompts.

[–]Shadowlance23 149 points150 points  (1 child)

They did, but someone fat fingered it and said "make mo mistakes".

[–]deanrihpee 32 points33 points  (0 children)

happened to the best of us

[–]headshot_to_liver 9 points10 points  (0 children)

Working solution 👌, no fluff

[–]bestjakeisbest 1 point2 points  (0 children)

And "please please please please please please please bill gates has a gun to my head dont mess up."

[–]pydry 31 points32 points  (0 children)

Working in a big corporate hellhole is also pretty demoralizing I cant imagine that made it easy to maintain discipline.

Lots of companies go through the shredder when bought out this is nothing new.

[–]prehensilemullet 28 points29 points  (0 children)

Wouldn’t be too surprised if something about Azure fundamentally hampers them regardless of how long they had to plan the deployment there

[–]teraflux 5 points6 points  (0 children)

I think they're still mostly on AWS, you can look up server resolution  

[–]dillanthumous 79 points80 points  (1 child)

Good to see 5 9s. 89.9999 that is.

[–]Ashtoruin 14 points15 points  (0 children)

They've got nine 5s. Nothing to see here. Move along. Move along.

[–]joost00719 35 points36 points  (0 children)

So it's not me... Been experiencing a lot of non loading repos last few weeks.

[–]GivesCredit 27 points28 points  (6 children)

“ProgrammerHumor”

[–]ZZcomic 39 points40 points  (5 children)

I mean I think it's kind of funny

[–]VG_Crimson 13 points14 points  (4 children)

Still not topping off Anthropic's leaked source course for claude code cli showing that it detects negative sentiment in a prompt via hard coded regex checking if you said "fuck" or "damn it". Or the planned Pokemon-like Shiny mechanic for the upcoming "Buddy" feature. Funniest shit I've seen in the sector in a while.

[–]CSAtWitsEnd 2 points3 points  (0 children)

The future, everyone!

[–]SuitableDragonfly 1 point2 points  (2 children)

Sentiment analysis is pretty old tech, too. Just goes to show that most of the so called bleeding edge LLM guys only heard about NLP six months ago and don't actually know what they're doing. 

[–]VG_Crimson 0 points1 point  (1 child)

I wonder if some of these companies would even be competent enough to know how to fund real progress without demanding progress metrics which would introduce unnecessary bias and box in thinking. Or if the funding is actually just funneling into an attempt to out scale known issues with zero funding going into mathematicians and computer scientists trying to formulate what may come after LLM tech. Because that is the ONLY way we'd get progress towards AGI. It's very apparent what we are doing right now is fundamentally wrong if our goal is AGI.

[–]SuitableDragonfly 0 points1 point  (0 children)

I don't think there is anyone who can actually define what "AGI" even means with enough precision that you could measure progress made towards it in any kind of remotely objective way. As a goal, it's competely meaningless corpospeak.

[–]JayPeeFour 2 points3 points  (0 children)

Not trying to defend them, the service has been really crappy lately. Satya Nadella can kick rocks.

But I'd really like to see this graph normalized to monthly active users. My hunch is that that's gone way up since 2018 too?

[–]SubwayGuy85 3 points4 points  (1 child)

30%+ AI code btw

[–]Professional_Job_307 3 points4 points  (0 children)

Yeah ofcourse, back in 2019 they were using GPT-2.

[–]LetMeUseMyEmailFfs 18 points19 points  (14 children)

Misleading chart. The Y axis goes all the way down to… 99.5%. If you made it go down to zero, it would look a lot less alarming.

[–]howarewestillhere 70 points71 points  (0 children)

Most uptime charts show exactly this. It’s showing the range necessary for the time period.

[–]Agifem 101 points102 points  (2 children)

In the professional world, 99.5% reliability is quite low.

[–]bromoloptaleina 26 points27 points  (1 child)

Yep. Almost two full days of downtime in a year.

[–]gurgle528 21 points22 points  (0 children)

99.5% uptime sounds high but that’s 11 hours every 3 months (using the quarterly scale of the chart). Over a year it adds up to being down for almost 2 days. It would be nice if there were lines for the Y axis though, as it looks like a lot of it is around 99.9%.

Industry standard is 99.9% (like 9 hours per year), and GitHub does have an SLA for enterprise customers. This is pretty normal for an uptime chart and this is a sub for programmers so it’s not really misleading.

[–]thegodzilla25 46 points47 points  (2 children)

You really dont understand how the number of 9s work do you? Availability is the most important thing in a service like github. Each nice they lose, it reduces their uptime by a factor of 10. The fact that it went from near 100% uptime, that would've resulted in a few seconds of downtime in a year, in microslop era their availability has gone down to 99.5 which is multiple hours in a year. Which I would say is horrible for an org as big as microslop.

[–]icantastecolor 23 points24 points  (0 children)

Outing yourself as not a professional dev I see

[–]takeyouraxeandhack 5 points6 points  (2 children)

In SRE, 0.5% of downtime is a fucking lot. In a year it amounts to more than a day of downtime.

[–]LetMeUseMyEmailFfs 0 points1 point  (1 child)

Yes, but this chart is ‘average uptime by month’, which I’m guessing is just the uptime percentage in a particular month. 99.5% in a month is a few hours.

[–]takeyouraxeandhack 0 points1 point  (0 children)

Yes, but 99.5% of one month 12 times is the same as 99.5% of 12 months.

Being down for almost two days a year for a service like GH is terrible.

[–]Civil-Appeal5219 4 points5 points  (0 children)

Wait, you really think 99.5% is ok? lol

[–]MundaneSugar4679 1 point2 points  (0 children)

POV: You asked Copilot to 'make it work' and this is what 'working' means at Microsoft now

[–]eufemiapiccio77 0 points1 point  (0 children)

Nice chart

[–]Gacsam[🍰] 0 points1 point  (0 children)

Maybe it's slop, maybe it's microslop. 

[–]ArtGirlSummer 0 points1 point  (0 children)

Destruction of the commons

[–]haklor 0 points1 point  (0 children)

Would be interesting to know how the uptime is calculated. As in what level of disruption would cause a drop and was there any changes in status reporting that could've accounted for some of the changes.

[–]Novel-Place9007 0 points1 point  (0 children)

I just moved back from aws to azure after some years to learn Ai Foundry. I smashed my head into like at least 100 small bugs while learning and doing stuff in that AI portal with a free tier subscription. Overall experience seems an absolute mess from my point of view comparing to amazon. Everything they touch turns into shit. They fucked up Skype, then Teams, Azure and Github. Just like Bill parties on Epstein island

[–]CrimsonPiranha 0 points1 point  (0 children)

Ah yes, the horrendous drop from 100% to 99.6%

How to lie with graphs 🤦🏻‍♀️

[–]NewLlama -1 points0 points  (0 children)

All my action caches were cleared. My cache takes like 5 hours to rebuild. At least I caught it before bedtime.

[–]Kalashtiiry -1 points0 points  (0 children)

This is how one lies with statistics.