I believe the bigger issue is when you have several other 3rd party services relying only on github like issue trackers and continuous integration/deploy... Then when this happens your workflow gets really messed up
I didn't think rubygems relies on github. And rubygems seems to be working fine to me at present.
It is true that rubygems runs on AWS and is effected by AWS outages (like much of the internet, it seems like).
It's also true that individual application Gemfiles can choose to express dependencies to gems hosted in a git repo, such as github, instead of the rubygems repository. If you don't want to be dependent on github, then don't do that. Of course, you're dependent on the rubygems repo ordinarily still, which has gone down occasionally. But the rubygems repository is independent from github.
It’s more karma whoring than anything else, this post doesn’t add anything except that GitHub is down and people who care about GitHub already know it, and those who don’t care, well, don’t care about this post.
I just noticed that a repository wasn't working, but hadn't put it together that the entire site might be down... so the karma whoring was useful for me.
Well some problems are slow downs instead of outright outages, and thats what the graphs are for since "response time" doesn't make much sense when no response is being sent at all.
Run it out to "month" and you can see cyclical, daily variation of response times and a general improvement from a slower than current state over the first week.
␄
Tangential graph criticism:
If you aren't going to put "zero" at the bottom of the Y axis, and you have graphs with only a single numbered data tick, then I have no idea whatsoever the value that correlates to a Y axis position. (except when it hits your label.) If you have fewer than 3 labeled data ticks then I don't even know if you are linear.
Starting your data at zero is a really good idea unless you really mean to be graphing the derivative, in which case, maybe you should just graph the derivative. The exception is when you have a constant offset in the concept you are graphing. Like atmospheric pressure on earth. But please give me at least three ticks and try to leave them consistently spaced if I'm every going to see another graph of them from you.
Including unlabeled ticks, evenly spaced, is a terse visual language that you are a linear graph.
I don't understand how anyone could outsource something as mission critical to their business as git hosting, issue tracking, etc to a third-party. If anything happened to github half the developer community would be hosed. Let's hope that never happens.
The same reason you outsource car maintenance to someone else: Because when there's a problem, there's a team of experts available to work on the problem, whom have far greater expertise to resolve it.
GitHub has a service that is meant to be highly available. What are the chances that 1/4th of the engineering effort would be placed in to a local solution?
Downtime is inevitable, and sometimes the thing that fails will cause huge problems and it's almost entirely unavoidable.
I'd much rather trust their team, which they've built to design the best service possible, to handle the infrastructure than having to use an internal team to design a competing product (albeit internal) with the same uptime requirements.
58 comments
[ 2.4 ms ] story [ 89.6 ms ] threadIt is true that rubygems runs on AWS and is effected by AWS outages (like much of the internet, it seems like).
It's also true that individual application Gemfiles can choose to express dependencies to gems hosted in a git repo, such as github, instead of the rubygems repository. If you don't want to be dependent on github, then don't do that. Of course, you're dependent on the rubygems repo ordinarily still, which has gone down occasionally. But the rubygems repository is independent from github.
␄
Tangential graph criticism:
If you aren't going to put "zero" at the bottom of the Y axis, and you have graphs with only a single numbered data tick, then I have no idea whatsoever the value that correlates to a Y axis position. (except when it hits your label.) If you have fewer than 3 labeled data ticks then I don't even know if you are linear.
Starting your data at zero is a really good idea unless you really mean to be graphing the derivative, in which case, maybe you should just graph the derivative. The exception is when you have a constant offset in the concept you are graphing. Like atmospheric pressure on earth. But please give me at least three ticks and try to leave them consistently spaced if I'm every going to see another graph of them from you.
Including unlabeled ticks, evenly spaced, is a terse visual language that you are a linear graph.
status.github.com
DNS, eh? Related to the recent CDN changes?
Not external, which would fall into the CDN-managed territory.
http://www.dynstatus.com/dynect-dns/5628/possible-dnssec-iss...
Downtime is inevitable, and sometimes the thing that fails will cause huge problems and it's almost entirely unavoidable.
I'd much rather trust their team, which they've built to design the best service possible, to handle the infrastructure than having to use an internal team to design a competing product (albeit internal) with the same uptime requirements.