The Real Blogger Status

This month started out with the termination of Old Blogger . And then the fun started. Problems which were carefully analysed, and aren't randomly experienced by all Bloggers. Very few have approached epidemic level proportions , but do have odd, non-random distribution. Several problems seem to be centered around Singnet in Singapore - Bloggers either directly paying for service from Singnet, or having ISPs that connect thru Singnet. This isn't the first time that Singnet has been involved. What is unique about Singnet, that it can cause misery to its customers so easily? How do we know that this weakness in Blogger - and that's what it is guys - a weakness - how do we know that this weakness won't be visited upon other Bloggers using other ISPs? Maybe any of us might be affected, at any time. Blogger needs to start telling us what is going on. But the Singnet problems aren't all that's disturbing us. From last month (and some time previous), we have the...

Blogger Support is telling us, repeatedly, that the Server Error 1-500-nn ("5nn") (and possibly the dashboard / post editor toolbar problem too ) is a Singnet (Singtel) problem. A possible workaround, using a proxy server owned by Singnet , was discovered by another Blogger. It appears that use of the workaround may be limited to direct customers of Singnet. Everybody victimised by the problem may not be helped by the workaround. And everybody victimised by the problem may not be in a position to complain to Singnet either. Bob isn't a Singnet customer - but his ISP connects through Singnet. No luck for him though. C:\>tracert www.google.com Tracing route to www.l.google.com [66.249.89.99] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 40 ms 43 ms 41 ms 10.122.84.253 3 42 ms 41 ms 43 ms 10.122.84.254 4 54 ms 55 ms 55 ms 10.121.20.1 5 * * * Request timed out. 6 51 ms 53 ms 51 ms 58.147.0.52 7 53 ms 51 ms 53 ms 58.147.0.46 8 268 ms 275 ms 271 ms 202.47.25...

I've been suspecting this for a while. We're seeing correlation between the two symptoms. >> In Status code: 1-500-19 , MeezNur writes the problem is solved... thanks somuch.. even the supposedly horizontal icons have returned to their original position.. >> Forum thread links: bX-*00041 >> Copy this tag: bX-*00041 >> Forum thread links: bX-*00042 >> Copy this tag: bX-*00042 >> Top

A lot of Bloggers are reporting these. This server is currently experiencing a problem. An engineer has been notified and will investigate. Status code: 1-500-nn Please visit the Blogger status page or the Blogger Knowledge Base for further assistance. or HTTP Status 5nn - Servlet NewFrontend is currently unavailable -------------------------------------------------------------------------------- type Status report message Servlet NewFrontend is currently unavailable description The requested service (Servlet NewFrontend is currently unavailable) is not currently available. -------------------------------------------------------------------------------- Apache Tomcat/4.1.24 Initial Diagnostics: Check how you are logging in to Blogger . Clear your cache and cookies . >> Blogger Employee has associated these errors, as earlier, with Singnet customers in Singapore . We have also heard from people in areas near Singapore, most likely using ISPs who get service through Singnet. To co...