4 ms·
It was a DDoS attack. Nothing to do with their infrastructure.
by kotnik 13y ago
It was a DDoS attack. Nothing to do with their infrastructure.
- tribaal 13y agoThe reminder still stands.
- shocks 13y agoSo?
- joeblau 13y agoYeah, but everything to do with their reputation. before 8 months ago, I never recommended Bitbucket to anyone. Now I do based on the knowledge that GitHub has a loss of connection at least once a month. The company I worked for used GitHub as the source for its build systems releases. If you can't do releases because GitHub is down a few times, I'm sure the dev/ops team will start looking elsewhere.
- zeckalpha 13y agoThe enterprise version of GitHub might be a middle ground.
- danieldk 13y agoOr Atlassian's Stash, which is is also really affordable for small teams.
- joeblau 13y agoYeah, that is a great point. Our lead ops guy was pushing for just hosting a bare bone git repository inside the firewall and not even buying a commercial product. Our problem was that we didn't have enough servers for our product, let alone our code.
- Diederich 13y agoGitHub enterprise has absolutely no dependencies on the mother ship, except for expiring license packs. And, in my experience, they'll very freely give you 1-2 month temporary packs, even if you're late with the renewals. Very good customer service.
- brokenparser 13y agoGitlab is easy to set up and it works really well. It has a much cleaner and pleasant interface as well (especially since GitHub ruined theirs about a month ago).
- Diederich 13y agoDefinitely agree. gitlab is just getting better and better.
- rfctr 13y agoIs there a good counter-measure against DDoS? I believe there is none. Commercial services help but only up to certain traffic level. Tomorrow Bitbucket can get under the same attack.
- joeblau 13y agoThere are some good counter measures. CloudFlare, the CDN that I'm using for my site http://gitignore.io http://gitignore.io helps mitigate DDoS's [1]. Github also took a good step by separating the source code domain github.com from the pages domain github.io [2]. I agree that tomorrow Atlassian could suffer a DDoS attack but I feel like since they are a more mature company, they have a lot more experience dealing with that type of attack. [1] - http://www.cloudflare.com/ddos http://www.cloudflare.com/ddos [2] - https://github.com/blog/1452-new-github-pages-domain-github-io https://github.com/blog/1452-new-github-pages-domain-github-...
- Thaxll 13y agoanycast + lot of bandwidth are the best solution against DDoS.
- aroch 13y agoThere comes a point where there isn't enough bandwidth you can buy...Reflection and amplification attacks can, very quickly, generate in the 100's of Gbps worth of traffic. IT simply isn't economical to keep that much bandwidth at hand all the time.
- pavs 13y agoAnd how will Bitbucket magically handle DDOS? Please do share. You are blaming Github for being attacked by DDOS?
- tootie 13y agoNot OP, but my last project on github ran for about 6 months and had at least 3 outages on the order minutes or hours. Didn't shut down the project, but it was worrisome and I don't think they were DDoS attacks.
- pavs 13y agoThat I can understand. If the comment was on a thread about github outage that was not DDOS related.