Skip to main content

403 Forbidden Woes Continue

During the weekend of May 10 - 11, 2008, many Blogger readers were having trouble viewing our blogs. Instead of seeing The Real Blogger Status (and various other blogs of greater and lesser importance), some unhappy folks were seeing a well known problem
403 Forbidden.
Pete Hopkins, the Google Man In The Know, described the cause of the problem - the side effect of a massive Denial Of Service attack against Google, as
Blogger is currently experiencing a high level of automated requests. In order to keep Blogger running smoothly for as many people as possible, we are blocking some IPs.
and continued with
Just because your IP is blocked does not mean that you or your network is making automated requests, you've just gotten caught up in the block.

We are working to remove the incorrect blocks as soon as possible.

Yet as of this evening, it appears that not everybody is back to normal.

It's possible that you, or your readers, who are affected by this problem will be able to get around it by using a proxy server. Though you won't be reading this, if you're affected by the problem. Sorry.

For additional insight into this problem, see Robertos Report: The 403 Block.

>> Forum thread links: bX-*00078

>> Copy this tag: bX-*00078

>> Top


Wil said…
Yep this is exactly what's happening for me I think for one of my blogs ( None of my archives work, and all posts (that WERE previously posted and displaying fine) from May 6 and May 8th suddenly aren't displaying at all. Everything is fine in the interface however. I also can't post anything new. It says it's published, but then just doesn't appear on the main page.

Where is the best place for me to go to let Blogger know my site is still not working?

Btw you ROCK for putting this message up here, I was going crazy thinking it was something wrong on my side.
Wil said…
One more question... come to think of it, I can view blogs, I just can't seem to view some posts on my own. Is this the same issue you're discussing here? Thanks again!
Chuck said…
Thanks, Wil, for the feedback.

The "403 Forbidden" seems to affect different blog readers in different ways. Possibly involving what blogs they are trying to access, possibly where they are connecting from.

Blogger isn't being too communicative right now. We may just have to grit our teeth and bear it. It's nasty, but there you have it.
Haloranch said…
I'm in Canada and my ISP is xplornet. It still seems to be blocked though I understand many service providers are now unblocked. How can I find out when ours will be unblocked? It's been over a week and I'm suffering blog withdrawal!

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: