If you can't read this, then you better read this:

I am told that Scienceblogs.com has upgraded and hardened its server thingies, so you should no longer be experiencing technical difficulties in reading your favorite blog. However, if you still are, please send your IP address to Scienceblogs, using this email: webmaster AT scienceblogs.com

Thank you very much. You may now return to your regularly scheduled disaster.

More like this

You may have noticed that Scienceblogs.com has been loading slowly lately. Also, in the "back end" .... where we write the blogs and stuff ... the servers have been slow, and eventually, useless. Well, the crack technical team that takes care of these things have determined that we were…
The latest information from management on the impairment of service: We are still working to contain the ongoing DDoS attack, and to this end we have recently upgraded our service with Rackspace. This should restore access to our readers who have been blocked for the last week. However, some…
You, my readers, have been complaining about flakiness in Sb that goes above and beyond the usual technical flakiness of the site. So have many other readers, in particular PZ's. After a couple of days where the blog loaded slow as the proverbial molasses in Minnesota in January, our benevolent but…
Dear Bloggers, We have been forwarding reports from bloggers and users to our hosting service, Rackspace, over the past few days. After monitoring our traffic and these reports, Rackspace has determined that ScienceBlogs is experiencing a distributed denial of service (DDoS) attack and has blocked…

I'm a Sb regular, and I didn't notice the DDoS, at any time.
Is there a technical reason why Canadian readers would be less affected than US ones ?

I've been sending my IP adress to the aforementioned mail adress daily for the last few days. I'm not going to keep doing that, since they've never been able to unlock my adress before I got a new one from my ISP.

I'll just stick to using Ultrasurf until they've sorted it out.

@Chroma: Thanks for the info.

While reading that thread did not convince me fully of US malicious nature, and all testing on my side with Wireshark, TCPView etc came up empty on malicious behavior, I'm gonna go hunting for a different lightweight solution anyway.

Any suggestions?