The successor to Gitosis.
Maybe I'm overly risk-averse, but I've been bitten a few times by Git setups that are non-standard or complicated and decided that it's far better to keep things as simple as possible. I'm not really interested in fiddling about keeping Git running smoothly, when it's incidental to the real work. It's just not worth it to save a few bucks, versus hosting a Git repo yourself on a VPS or something.
Edit: It was just one spike that went down to 0, directly after it there's a higher spike. (It didn't change the mean response time of 113ms, though)
"0:18 UTC GitHub.com is recovering at this time from a DoS attack. We're continuing to monitor things and will provide further updates as the situation develops."
Is there really no way to protect from these attacks!?
DDoS protection services exist that forward the good traffic on to you, and they do this by having excessively large amounts of bandwidth. They also cost obscene amounts of money.
(disclaimer: I'm a google employee, but not on the page speed service).
[1] https://developers.google.com/speed/pagespeed/service/faq#mo...
[2] https://developers.google.com/speed/pagespeed/service/pricin...
Surely GitHub must have the money to beef up their pipes, no? Or perhaps they're noticing that these outages aren't really hurting their bottom line, and thus it's not worth the investment...
2. Usually blackmail.
