GitHub was down • Hacker News Board

Re: GitHub was down

#71

Post by jaekash » Mon, Jul 13, 2020, 7:35 AM UTC

quyleanh wrote: post #60

I still don't understand people who always mentions to Microsoft's acquisition. Until the official statement, it isn't Microsoft failure. Don't blame them.

You know if you use Microsoft products every day, and every day they let you down, and every day you experience the worst most unintuitive design in the world, and every day you have to deal with their reliability issues, and then MS acquires github, and github starts to behave like everything else MS touches ...

Clearly something about how MS runs is responsible for their past outcomes, why is it a stretch to assume it is responsible for another similar outcome?

It is like saying we don't know the rotation of the earth is why the sun rose this morning because we have not had an official investigation into the matter.

Re: GitHub was down

#72

Post by hnarn » Mon, Jul 13, 2020, 7:36 AM UTC

MattGaiser wrote: post #66

quyleanh wrote: post #60

I still don't understand people who always mentions to Microsoft's acquisition. Until the official statement, it isn't Microsoft failure. Don't blame them.

It’s a pattern. GitHub is now down a lot.

I have to agree that this feels like an abnormal amount of downtime the past few months -- it would be interesting to see some actual data over a longer term.

Re: GitHub was down

#73

Post by lord_erasmus » Mon, Jul 13, 2020, 7:36 AM UTC

quyleanh wrote: post #60

I still don't understand people who always mentions to Microsoft's acquisition. Until the official statement, it isn't Microsoft failure. Don't blame them.

The following article has been shared in HN recently, so there's some ground to those claims

https://nimbleindustries.io/2020/06/04/has-github-been-down-...

Re: GitHub was down

#74

Post by noble_pleb » Mon, Jul 13, 2020, 7:38 AM UTC

mundanevoice wrote: post #54

Move off Rails now GitHub, is clearly not working for you. It took you this far, now go move to something that doesn't sh*ts the bed twice every month.

Flask (python) or even CodeIgniter (php) are my frameworks of choice for this sort of thing. They may be a bit old and organizing a large project could be difficult but nothing can beat them on performance!

Re: GitHub was down

#75

Post by dijit » Mon, Jul 13, 2020, 7:41 AM UTC

hnarn wrote: post #72

MattGaiser wrote: post #66

Earlier quoted context omitted.

It’s a pattern. GitHub is now down a lot.

I have to agree that this feels like an abnormal amount of downtime the past few months -- it would be interesting to see some actual data over a longer term.

https://nimbleindustries.io/2020/06/04/has-github-been-down-...

97% increase in minutes of downtime since Microsoft.

Could be better reporting now though.

Re: GitHub was down

#76

Post by mindfreeze » Mon, Jul 13, 2020, 7:42 AM UTC

I am thinking when was the last time GitLab went down, I rarely or did not see downtime experience like this bad with Gitlab, I was seeing history,

https://status.gitlab.com/pages/history/

They do have some latency or slowness issues, but couldn't find like whole system down thing,

Like in one of the comments here, reminded me of 2017 incident, https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab... They should have improved a lot by now, but still I am curious, why such large or frequent downtimes are happening to GitHub. Is it due to making it more open for teams with Private repos, and more perks along with quarantine and WFH things

Re: GitHub was down

#77

Post by quyleanh » Mon, Jul 13, 2020, 7:43 AM UTC

jaekash wrote: post #71

quyleanh wrote: post #60

I still don't understand people who always mentions to Microsoft's acquisition. Until the official statement, it isn't Microsoft failure. Don't blame them.

You know if you use Microsoft products every day, and every day they let you down, and every day you experience the worst most unintuitive design in the world, and every day you have to deal with their reliability issues, and then MS acquires github, and github starts to behave like everything else MS touches ... Clearly something about how MS runs is responsible for their past outcomes, why is it a stretch to assume…

It's just your own feelings. I haven't had any issue with Microsoft products (and yes I use their services every day in my working life). All I can see from you is making a guess with your full of sentiments and negative thoughts. So as I said, don't blame them until official statement.

Re: GitHub was down

#78

Post by echelon » Mon, Jul 13, 2020, 7:44 AM UTC

Well, there goes my night. I was waiting on a build triggered by Github actions and was wondering what was up.

I guess this is my sign to get some sleep.

Microsoft needs to slow things down and focus on stability. This really isn't good. I need these weekend and late night hours for my side hustle. I already have enough trouble as is, I don't need an injection of additional difficulty. (That's just my frustration; I can't imagine what y'all are all going through.)

They're making some very frustrating choices lately. Their redesign broke READMEs with tables (which now require horizontal scrolling), and they don't seem to care about all the repos they impacted.

Pull it together, Microsoft.

Re: GitHub was down

#79

Post by brobinson » Mon, Jul 13, 2020, 7:44 AM UTC

mundanevoice wrote: post #54

Move off Rails now GitHub, is clearly not working for you. It took you this far, now go move to something that doesn't sh*ts the bed twice every month.

Rails is (apparently still) a popular target for haters, but for projects at Github's scale it's rarely a code logic/framework-level blunder that's taking the service down. It's generally a cascade of failures in things like multiple database systems, auto-scaling, dns/caching, etc.

Re: GitHub was down

#80

Post by dijit » Mon, Jul 13, 2020, 7:44 AM UTC

gregoriol wrote: post #59

flukus wrote: post #40

Earlier quoted context omitted.

Very often that's ok if you can choose when the outages occur. With most you can because outages tend to be for regular maintenance and upgrades far more often than hardware failures. A small geographically concentrated company only needs 9 fives. Even for bigger companies that need more uptime they can at least give a shout out to everyone that it will be unavailable from X to Y, it doesn't just go down randomly wit…

If you think self-hosting doesn't randomly go down, you have never done self-hosting. In the last few months we had a server that physically crashed and had to be replaced, we had a bad kernel that paniced randomly and a gitlab upgrade that failed in the middle. Is you team equiped and ready to handle these? If not, don't self-host anything critical to your company, or your costs, downtimes and losses will be much mu…

this always comes up, and it's one of those things that's obviously true on the surface until you understand context.

I have a self-hosted gitlab instance and it has much higher uptime than github in the last year. At some point a weekly downtime is going to trump any potential random outages.

The major difference might be your ability to affect those outages (positive or negative) because humans are the primary cause of outages, and you can restore service to a gimped passable state if its your own thing.