Because my comment isn't clear. This is not an interesting news. A link to the twitter status or the github status (https://status.github.com/messages) would be relevant in that case. not just some link to a third party telling us it's down. Yeah thank you. I could have notice it on my own....
Probably because they said they are under a large ddos attack? :-?
I wonder why would someone do something like this? It's not like github is evil or anything... it's just a really cool and useful tool for coders. It helped a lot of people better their skills and knowledge. Why would someone attack it? (I am genuinely interested in this as I can't think of a reason someone would do something like this)
You didn't get his point. The submitted URL doesn't provide useful information, https://status.github.com/messages could have been used instead.
May be when the link was submitted the official information wasn't available. OK, then just wait for something useful because if the site is down and I'm affected I can see that myself, I don't need to read HN.
EDIT: oh, looks like the original comment was edited.
Because tragically, most people have all their eggs in one github shaped basket.
Git on it's own doesn't suffer from the issue of scary downtime (occasionally repo corruption...), but people have bought deeply into the value-added ecosystem that github throws over the top of it.
I have some of my code on GitHub and some on Bitbucket (for the free private repos), all of my code on my Dropbox and it's synced to 4 different machines.
However, the library I'm working with is hosted on GitHub, their doxygen is on GitHub, their wiki is on GitHub, and I don't have a local version of either of those, which is now pretty annoying.
Very true. This is a major irritation. I rather like Golang because of stuff like this as you can run your own local documentation server and stuff. It's just a neat self-contained package.
It's not, really. But I assume a good number of us have jobs that depend on it, and out of the big sites out there they are out quite frequent. And then like past threads this one will fill up with people proclaiming they're done with Github and having enough of their shit and looking for alternatives...
Why not? They likely already have a botnet, they didn't make it to DDoS GitHub specifically. Maybe they were annoyed with someone who was using GitHub, or they wanted to prove a point, who knows. All in all, the reason is because they can.
My intuition would be that status.service.com is not a useful place to look if service.com is down...
edit that's not supposed to be as snarkey as it sounds reading it back :-)
edit again The reason for this intuition is that I assume that not being able to reach service.com could indicate a DNS problem. Possibly from the comments below I need to go and read a DNS book :-)
My intuition is that it is. I didn't know github was really down, but had problem accessing it. Went to status.github.com and got the results, not really knowing if the address existed or not (just guessed).
These sites are often hosted away from the main service, and thus available even when problems occur.
Wouldn't it be a good idea for Github to set up a video + sound stream from their office when these things occur? I for one would watch. Can't really work anyway (at least that's what I persuade myself to think).
Maybe they would, but I'm sure a bunch of people would also be wondering why they waste their time on putting on a show instead of fixing their core business :P
Alright, perhaps ordinary web cams on the faces of the employees involved? Just seeing the hard work and stress in their eyes would be pretty soothing. That might be an idea for any site: "We're currently down, but here are the faces in real-time of our engineers trying to fix it".
Where are these attacks coming from? Or is it just failure to keep up with increased client traffic?
I've noticed recently how frequently there are service issues with Github, many times service has been disrupted because of DDoS attacks and similar malicious activity.
One reason I like them is that it's easy to pull your hair out trying to figure out why something isn't working without checking an obvious (but not entirely likely) cause.
Good thing about decentralized version control systems is that they're decentralized.
I hope github can deal with today's issue without too much trouble, but it's not a major inconvenience to me and the rest of my company's devs. We can just push and pull changes to some convenient in-house server via ssh to sync up our work.
That's true, it's a problem when you depend on having the repository at a specific location or depend on something that's not in the repo, like wiki or issue tracking, as mentioned in the other comments.
I just wanted to express my appreciation that github being down is not as big an issue for most people as it would be if github was cvshub or svnhub. :-)
"12:44 UTC We've put mitigation in place that should deflect the attack, and services are recovering. We're continuing to monitor closely." - https://status.github.com/
I put all my personal projects on BitBucket and GitHub (and sometimes CodePlex for the comunities into that sort of thing) and just push to all of them. Never ever had both down at the same time (in fact I don't think BitBucket has gone down once since I started using it). There are multiple free git hosting sites no reason not to use them all at once.
Because my comment isn't clear. This is not an interesting news. A link to the twitter status or the github status (https://status.github.com/messages) would be relevant in that case. not just some link to a third party telling us it's down. Yeah thank you. I could have notice it on my own....
reply