/enqueue jokes about decentralized DVCS systems being hosted centrally...
Srsly tho, the relationship between Git and GitHub, might be somewhat analogous to that of BitTorrent and TPB
Github: Major Service Outage
51–60 of 80 posts
Re: Github: Major Service Outage
#52Re: Github: Major Service Outage
#53/enqueue jokes about decentralized DVCS systems being hosted centrally... Srsly tho, the relationship between Git and GitHub, might be somewhat analogous to that of BitTorrent and TPB
I call it recentralized.
Re: Github: Major Service Outage
#54Why do people always post on Hacker News whenever Github is offline? It's not going to make Github go online any quicker. They have a Twitter account, you know.
It's a site most people here use, and it's interesting. It's not about getting things back up faster, but letting people know what's going on and giving them the chance to witness how a large site fails and recovers.
Re: Github: Major Service Outage
#55First off, as others have said, disabling port 80 is a great way to handle this, I don't really care that much if I can see/use github the website for a few hours, but I'd be much more upset if I couldn't pull my code. Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.
They didn't even disable https, so the site was still fully usable.
Re: Github: Major Service Outage
#56I think it's probably my fault. Github seems to go down every time I start poking around in someone else's projects.
By any chance, did you 'poke' with a cluster of LOICs?
(Never heard that term before...)
Low Orbit Ion Cannon (LOIC) is an open source network
stress testing and denial-of-service attack application
[...]
LOIC performs a denial-of-service (DoS) attack (or when
used by multiple individuals, a DDoS attack) on a target
site by flooding the server with TCP packets or UDP
packets with the intention of disrupting the service of a
particular host. People have used LOIC to join voluntary
botnets.
Re: Github: Major Service Outage
#57Earlier quoted context omitted.
It'd be glorious if one service (say GitHub) had multiple remote links that dynamically switched for you when service faced an outage.
If it's one service though there is still always a single point of failure outside of your control. If you want true redundancy you need to use multiple versions with no interconnections and develop your own solution to mitigate partial failure, of course your own solution is also a single point of failure, but at least it's under your control. That said, Github has never been down long enough for me to justify a fal…
There will be no crossing if the bridge is down, though.
Re: Github: Major Service Outage
#5801:41 PM PST We've temporarily disabled service on port 80 while we investigate the source of a connection flood. HTTPS, GIT, and SSH service are unaffected. 01:33 PM PST "We are experiencing issues due to a DDOS attack, working hard to restore service"
I'm reading over the status updates a few hours after the fact, but for some reason the 1:33PM stands out because it is wrapped in quotes. Probably minor and meaningless. Just noted because it's different from the others.
Re: Github: Major Service Outage
#59First off, as others have said, disabling port 80 is a great way to handle this, I don't really care that much if I can see/use github the website for a few hours, but I'd be much more upset if I couldn't pull my code. Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.
> "disabling port 80 is a great way to handle this"
It's been a disaster for a bunch of people I know.
git is distributed by nature so they all had extra remotes they could use.
github's issues and other project metadata wasn't distributed, since that's github's alone.
So all of the friends of mine who are corporate github users who were using git in a distributed style (a minority of their overall customer base, I would suspect) are more screwed by the web app's absence than they would have been by a repository problem.
I suspect github made the right choice for their customer base overall, but I still find the anecdata interesting.
Re: Github: Major Service Outage
#6001:41 PM PST We've temporarily disabled service on port 80 while we investigate the source of a connection flood. HTTPS, GIT, and SSH service are unaffected. 01:33 PM PST "We are experiencing issues due to a DDOS attack, working hard to restore service"
I'm reading over the status updates a few hours after the fact, but for some reason the 1:33PM stands out because it is wrapped in quotes. Probably minor and meaningless. Just noted because it's different from the others.
It's because we update the status site from our chat room via Hubot and whoever posted that particular update didn't realize that they didn't need to put quotes around the body of the message.