@nikrichie well of course you will need to get some sort of protection to start with.
-
-
Replying to @JusticeSquad_
@JusticeSquad_ no you are wrong. You are just proving you have no idea what is happening.2 replies 0 retweets 0 likes -
Replying to @nikrichie
@nikrichie we can not control the actions of others.1 reply 0 retweets 0 likes -
Replying to @JusticeSquad_
@JusticeSquad_ first honest thing you've said to me. Thank you.1 reply 0 retweets 0 likes -
Replying to @nikrichie
@nikrichie we are still taking credit for the initial attacks which were on the IP: 216.218.193.31 reply 0 retweets 2 likes -
Replying to @JusticeSquad_
@JusticeSquad_ ok I will give you that.@CloudFlare sucks.2 replies 0 retweets 0 likes -
Replying to @nikrichie
@nikrichie@CloudFlare we are unsure who is attacking your current IP: 205.237.202.177 as we have stopped our attacks.1 reply 0 retweets 0 likes -
Replying to @JusticeSquad_
@JusticeSquad_@CloudFlare waste of time talking to CF they are too commercial and can't defense against real hackers. Right JS.4 replies 0 retweets 0 likes -
Replying to @nikrichie
@nikrichie We can't help if your IP is being attacked directly. Some tips to mitigate the risk of your server IP being found:1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare I pay you not to help. I get it. You guys are a scam. 20 days of failure. Thanks for nothing.3 replies 0 retweets 2 likes
@nikrichie We have many sites that have successfully fended off a DDoS attack utilizing CloudFlare. If your IP was being attacked directly
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.