probably not much. it's not like they (or anyone) has the resources to handle much projected overload.So how large of a ddos attack do you need to hamper a site that probably has a gazillion hits a minute anyhow?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
probably not much. it's not like they (or anyone) has the resources to handle much projected overload.So how large of a ddos attack do you need to hamper a site that probably has a gazillion hits a minute anyhow?
probably not much. it's not like they (or anyone) has the resources to handle much projected overload.
I believe the context I was responding to was whether anyone could actually bring down Google's servers with a DDoS attack under the belief that Google has tons of resources to take the load.best they can do is phish out the passwords. thats about it and that wouldnt affect google itself.
My point is that a substantial DDoS attack can bring Google's servers down because they don't have enough resources online to take that kind of overload.
Yes, I'm willing to bet that no one, not even Google, has servers idling in a farm somewhere to handle the theoretical threat of a substantial DDoS attack. If you've got information refuting that business reality beyond mere speculation by all means post it up for everyone here to consume.Do you want to bet on that? Anon thought the same with Amazon. They were, as usual, wrong. Google does not actually have the amount of resources as Amazon, but they are not too far behind and an Anon DDoS would be a fart in the wind.
Yes, I'm willing to bet that no one, not even Google, has servers idling in a farm somewhere to handle the theoretical threat of a substantial DDoS attack. If you've got information refuting that business reality beyond mere speculation by all means post it up for everyone here to consume.
Simply having "spare servers idling in a farm" is not the only, nor necessarily, the most effective way of mitigating a DDoS attack that Google could/would/does employ. Amazon survived Anon's "substantial DDoS" that we are discussing, so you already are incorrect on "anyone".
well perhaps instead of trying to get into a pissing match with me over this you'd instead scroll up and read my response and the question that elicited it as neither have anything to do with anonymous specifically.Simply having "spare servers idling in a farm" is not the only, nor necessarily, the most effective way of mitigating a DDoS attack that Google could/would/does employ. Amazon survived Anon's "substantial DDoS" that we are discussing, so you already are incorrect on "anyone".
well perhaps instead of trying to get into a pissing match with me over this you'd instead scroll up and read my response and the question that elicited it as neither have anything to do with anonymous specifically.
No, you're incorrect. Google already succumbed to DDoS in 2009. Their Google+ servers are nowhere near established enough to handle a substantial DDoS attack.Google's "theoretical" and Amazon's proven ability to respond to large DDoS attacks have nothing to do with Anon specifically either, they simply exist as part of their business and run counter to your assertion. So don't worry it's not a pissing match, just a correction to an incorrect supposition that you presented. Peace, love, dope my friend.
Google probably knows all of the members by name.
No, you're incorrect. Google already succumbed to DDoS in 2009. Their Google+ servers are nowhere near established enough to handle a substantial DDoS attack.
You incorrectly attributed my statement to mean that anonymous could launch such an attack when in fact I made no such assertion. Then you attempted to use their failed attack on Amazon as evidence of your assumption that Google has the same capacity.
The only conclusion you can draw from your evidence is that anonymous did not have enough resources to launch a substantial enough attack on Amazon. That has no relevance to Google's servers.
Furthermore, your responses don't even address my claim that Google isn't impervious to a substantial amount of traffic. What I said is absolute fact--even Google doesn't have the resources to handle a substantial enough attack. You can try and "correct" me all you want about whether anonymous would be able to launch such an attack but the point you seem to be missing is that I never claimed they did so kindly move along.
No, you're incorrect. Google already succumbed to DDoS in 2009.
Their Google+ servers are nowhere near established enough to handle a substantial DDoS attack.
Furthermore, your responses don't even address my claim that Google isn't impervious to a substantial amount of traffic. What I said is absolute fact--even Google doesn't have the resources to handle a substantial enough attack. You can try and "correct" me all you want about whether anonymous would be able to launch such an attack but the point you seem to be missing is that I never claimed they did so kindly move along.
Yes, I'm willing to bet that no one, not even Google, has servers idling in a farm somewhere to handle the theoretical threat of a substantial DDoS attack. If you've got information refuting that business reality beyond mere speculation by all means post it up for everyone here to consume.
@mope54
How do you know what their network capabilities are half-way through 2011 are? Or how much they have invested in security? One specific event over 2 years ago isn't worth a crap.
Not Agreeing or Disagreeing with either of you two, but just three weeks ago Google+ closed invitations to their service due to "insane demand."
Publicity stunt.
People want things they can't have.
Publicity stunt.
People want things they can't have.
It also doesn't help your case when they've admitted to running out of space on their servers before...
evidence.
Wow...the system setup to handle notifications ran out of space faster than Google calculated for early beta testing of Google+.
It does not show that they would fall to an attack by an outside source attacking. Honestly, the worse I see happening to Google if anyone did try to attack them would be slow connectivity to Google services.
Does any company encrypt anything on their servers? ...what the heck is wrong with these corporations does it take an insane amount of overhead to encrypt our gmail and other services?
Hi there. The follow up article was with respect to the accusation that Google's Stop-Invite activity was not likely a publicity stunt, but rather due to actual technical reasons. I am, and certainly was not, implying anything about Google's ability to handle traffic, as that tends not to be even remotely close to disc space management. The two are completely unrelated (Network traffic =/= ROM).
I do however have an article pertaining to their ability to handle incoming Google+ accounts within a period of time cited earlier than the post you are referring to. Feel free to contest me on that.
Is the lock out a publicity stunt? I have no idea, nor do I care.
I was referring to the question that Google had issues with Google+ already when in fact it was just hard drive space on notifications which was minor.
It does not show that they would fall to an attack by an outside source attacking.