Quick update on this... Our server is on Layered Technologies who also host wordpress.com and other wordpress sites. So it is almost certainly related.
See http://uptime.netcraft.com/up/hosted?netname=NETBLK-PLNT-LT-12,67.18.187.0,67.18.187.255
Layered Tech's response: "We did have some blocks in place in response to the WordPress DDoS attacks that impacted some APNIC ASNs in New Zealand. The blocks were removed at 1 PM CST (GMT-6) on 3/7/11. "
doozy: I've had confirmation that the purge is done and the blocks removed.
Many thanks for your help.
Out of interest, is "IP address blocking" cached somehow, or is it just the routes being referred to in this case? So, in order for my connection to WordPress to be reinstated, did their provider have to specifically remove the blocks, then my ISP (Telecom) had to refresh routing? From my perspective, the connection was available as soon as WordPress advised me (within minutes).
I am just trying to understand in case I have the misfortune of experiencing this problem again.
Also, someone mentioned earlier that, as a static IP address holder, I can request to bypass "the cache". Is this correct, and is this advisable? I am not sure that it would have been helpful in this case. Even if I had access, I would have been blissfully unaware of others not being able to see our site.
doozy: I've had confirmation that the purge is done and the blocks removed.
Many thanks for your help.
Out of interest, is "IP address blocking" cached somehow, or is it just the routes being referred to in this case? So, in order for my connection to WordPress to be reinstated, did their provider have to specifically remove the blocks, then my ISP (Telecom) had to refresh routing? From my perspective, the connection was available as soon as WordPress advised me (within minutes).
I am just trying to understand in case I have the misfortune of experiencing this problem again.
Also, someone mentioned earlier that, as a static IP address holder, I can request to bypass "the cache". Is this correct, and is this advisable? I am not sure that it would have been helpful in this case. Even if I had access, I would have been blissfully unaware of others not being able to see our site.
You could host it in NZ which should prevent this problem, which I am sure has cost you a lot in time.
Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.
doozy: I've had confirmation that the purge is done and the blocks removed.
Many thanks for your help.
Out of interest, is "IP address blocking" cached somehow, or is it just the routes being referred to in this case? So, in order for my connection to WordPress to be reinstated, did their provider have to specifically remove the blocks, then my ISP (Telecom) had to refresh routing? From my perspective, the connection was available as soon as WordPress advised me (within minutes).
I am just trying to understand in case I have the misfortune of experiencing this problem again.
Also, someone mentioned earlier that, as a static IP address holder, I can request to bypass "the cache". Is this correct, and is this advisable? I am not sure that it would have been helpful in this case. Even if I had access, I would have been blissfully unaware of others not being able to see our site.
Well, I do not know the answer regarding the IP blocking being 'cached' for sure, it certainly seemed that 'bad' responses were being cached. I will ask the cache king.
As a static IP address holder yes you can request to bypass the caches should you want to.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
