Github's not only Git. Lots of services integrate with Github. Stuff like continuous integration, continuous deployment. If your system is built on those things, Github being down will prevent you from deploying.
What's the alternative, replicate everything in-house/self hosted? Should startup stop using third party service providers?
How do you know when that point is? Is there even data out there on how frequently big providers go down? (Not just Github, but stuff like aws, etc)
Generally, you don't care if GitHub [or your inhouse equivalent] is down when no one is working. Also, if it goes down in the middle of the night and the first guy in fixes it...the difference between 1 man hour down in the morning vs. 20 man hours during the day across an entire team is significant.
There are very valid reasons for both choices.
Let's see who the Saturday team is!
per docs at https://github.com/bower/bower oh....
As for the docs, it is somewhat crazy to think how much documentation is hosted by GitHub these days...
Even if they were only updated every 24 hours and had a limited history for each repo, it still seems like it would be a really useful fallback that they could put up when things like this happen.
I still have the tab opened now, saying "All systems operational"...
I've personally wondered about their stack but I imagine that has little to do with that--mostly Ruby though right?
"github.com is currently unreachable. We are investigating mysql cluster issues."
https://gist.github.com/kyledrake/e6046644115f185f7af0
More info:
http://www.theverge.com/policy/2014/5/9/5699510/web-hosting-...
