Numerous Bloggers, in various threads, are reporting inability to connect with Blog*Spot. This is similar to previously observed problems in China, Pakistan, and other places.
The problem is affecting various ISPs in multiple, widespread areas of the UK geographical region - all areas - England, Ireland (Northern and Southern), Scotland, and Wales - appear to be affected. The problem, as reported, only affects access to "blogspot.com", not to "blogger.com".
One Blogger in the UK has done a connectivity test, which appears to rule out an outright traffic block.
The problem has been seen by Blogger staff, and has now been acknowledged.
For more information, and a master thread list:
For those who cannot access Blog*Spot, this page may also be available as
http://www.pkblogs.com/bloggerstatusforreal.blogspot.com/
2007/03/connectivity-problems-with-blogspot.html
or as
http://w1.hidemyass.com/index.php?
q=http%3A%2F%2Fbloggerstatusforreal.blogspot.com
%2F2007%2F03%2Fconnectivity-problems-with-blogspot.html&hl=3e5
(remove gratuitous line breaks in URLs, after you copy the text).
(Update 2/10): The problem is still active, but (almost) all complaints are from Virgin / Telewest customers. What was done by Blogger Support previously is a mystery.
(Update 2/7 19:00): Blogger Employee has modified the previous advice to
(Update 2/7 9:00): Blogger Employee now recommends that Bloggers work directly with their ISPs to resolve this issue.
(Update 2/6 18:00): Several UK Bloggers indicate that, even after clearing cache, the problem is not resolved.
(Update 2/6 12:00): Blogger states that this has been sorted out and fixed, though from experience it appears clearing of cache and cookies may be required.
(Update 2/5 10:00): Blogger staff continue to work on this issue, and acknowledge that the problem is not solved.
(Update 2/4 17:00): Blogger staff have instituted a network workaround for the problem.
>> Forum threads: bX-*00003
>> Copy this tag: bX-*00003
>> Top
The problem is affecting various ISPs in multiple, widespread areas of the UK geographical region - all areas - England, Ireland (Northern and Southern), Scotland, and Wales - appear to be affected. The problem, as reported, only affects access to "blogspot.com", not to "blogger.com".
One Blogger in the UK has done a connectivity test, which appears to rule out an outright traffic block.
The problem has been seen by Blogger staff, and has now been acknowledged.
For more information, and a master thread list:
For those who cannot access Blog*Spot, this page may also be available as
http://www.pkblogs.com/bloggerstatusforreal.blogspot.com/
2007/03/connectivity-problems-with-blogspot.html
or as
http://w1.hidemyass.com/index.php?
q=http%3A%2F%2Fbloggerstatusforreal.blogspot.com
%2F2007%2F03%2Fconnectivity-problems-with-blogspot.html&hl=3e5
(remove gratuitous line breaks in URLs, after you copy the text).
(Update 2/10): The problem is still active, but (almost) all complaints are from Virgin / Telewest customers. What was done by Blogger Support previously is a mystery.
(Update 2/7 19:00): Blogger Employee has modified the previous advice to
We're going to continue to investigate this problem and see what we can do to come to a resolution, but it's tricky because the fault lays on the specific ISPs you all are using, not the Blogger application.
(Update 2/7 9:00): Blogger Employee now recommends that Bloggers work directly with their ISPs to resolve this issue.
I recommend trying to work with your internet service provider (Virgin Media or whoever it may be) to get to the bottom of this issue.
(Update 2/6 18:00): Several UK Bloggers indicate that, even after clearing cache, the problem is not resolved.
(Update 2/6 12:00): Blogger states that this has been sorted out and fixed, though from experience it appears clearing of cache and cookies may be required.
(Update 2/5 10:00): Blogger staff continue to work on this issue, and acknowledge that the problem is not solved.
(Update 2/4 17:00): Blogger staff have instituted a network workaround for the problem.
>> Forum threads: bX-*00003
>> Copy this tag: bX-*00003
>> Top
Comments