Looks like they are fine now. Yay!
> We continue to investigate the issues with GitHub services and will shift to a slower update cadence to provide more meaningful updates going forward.
Posted 18 minutes ago. Feb 27, 2020 - 16:12 UTC
GitHub was down
91–100 of 171 posts
Re: GitHub was down
#92Earlier quoted context omitted.
Still miles better than BitBucket.
When was the last time BitBucket had an outage? Personally I don't see a lot of difference between the two platforms; or GitLab (my primary now). Github probably has the best UI, but Gitlab's has gotten a lot better; and there are always self hosted solutions like Gogs.
I'm pleased I don't have to deal with BitBucket any more, but back a year or two it felt like it had an outage that impacted work at least once every six months. Sure that might not sound like much, but it was always a pain.
Plus of course the service was so damn slow that using it was a daily pain.
Re: GitHub was down
#93That explains why my test suite suddenly takes >1h and after I canceled it, the status was green O.o
Re: GitHub was down
#94This seems to be the third or so day in the past week I've had issues with GitHub around this time in the morning. They've typically been really good. I'm a bit surprised there hasn't been more talk about it on HN.
Still miles better than BitBucket.
Sure, but not better than Gitlab.
Re: GitHub was down
#95What do you guys recommend as a good way to continue work undisrupted when GitHub goes down? A second remote mirror?
Re: GitHub was down
#96Are they migrating to azure?
I had the same guess... migrating from aws to azure & hitting some bumps. Have to assume they won't be very forthcoming about it if that is the reason.
Re: GitHub was down
#97Don't forget to check your SLAs Enterprise = 99.95% (quarterly) https://help.github.com/en/github/site-policy/github-enterpr... They're having a bad February but January was good. We will see what March has in store
> How do we calculate Uptime? > Our Uptime calculation is based on the percentage of successful requests we serve through our web, API, and Git client interfaces. Just curious, how do they measure this? What is the actual calculation?
> What is the actual calculation?
Not answering this directly, but the paper Meaningful Availability [0] released recently really changed my opinion on how to calculate and visualize availability. There's a discussion on HN as well [1].
[0]: https://www.usenix.org/system/files/nsdi20spring_hauer_prepu... [1]: https://news.ycombinator.com/item?id=22424173
Re: GitHub was down
#98What do you guys recommend as a good way to continue work undisrupted when GitHub goes down? A second remote mirror?
A second mirror doesn't really help - when github goes down, the code should still be available locally on your computer. The things that become truly available when github dies are all the non-git features: issues, PRs, etc...
There are several ways to work around this, but none are really satisfying.
Re: GitHub was down
#99Earlier quoted context omitted.
> How do we calculate Uptime? > Our Uptime calculation is based on the percentage of successful requests we serve through our web, API, and Git client interfaces. Just curious, how do they measure this? What is the actual calculation?
Same here. They obviously don't have beacons on the client side, I wonder if it's based on statistics, at this time of the day on a Tuesday we should be getting x requests but are getting only x/n.
> They obviously don't have beacons on the client side
Says who?
Re: GitHub was down
#100Earlier quoted context omitted.
"You can't legislate against failure, but you can focus on fast detection and response" -- Chris Pinkham
It’s amazing how this is accepted in the software world. Move fast and break things, such a different philosophy to other areas.
It’s evolutionary pressure; software is malleable and potential functionality is limitless. Software companies that didn’t ascribe to this philosophy were repeatedly killed by ones that did until it became the status quo.