How many of YOUR pings are getting through?

[BigSmile]

Hi,

I noticed that quite a few of my pings are not getting through? Is this normal or do I have something set wrong? If it makes a difference mu blog is setup in a folder and not on the root domain...

Not sure what those codes mean? I want the search engines to find me so I need all the ping help I can get

Here are my logs. You can find your logs under:

OPTIONS -> Smart Update Pinger

They should be listed at the bottom of the page...


My Ping Logs:

http://rpc.pingomatic.com was successfully pinged (extended format)
http://www.blogpeople.net/servlet/weblogUpdates was successfully pinged (extended format)
http://bulkfeeds.net/rpc was successfully pinged
http://ping.myblog.jp was successfully pinged (extended format)
http://ping.bloggers.jp/rpc/ was successfully pinged
http://bblog.com/ping.php was successfully pinged (extended format)


http://ping.weblogs.se/ could not be pinged. Error message: “transport error - could not open socket: 0 Success”
http://blogmatcher.com/u.php could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
http://coreblog.org/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
http://trackback.bakeinu.jp/bakeping.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
http://ping.bitacoras.com could not be pinged. Error message: “parse error. not well formed”
http://ping.blogmura.jp/rpc/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
http://xmlrpc.blogg.de could not be pinged. Error message: “transport error - HTTP status code was not 200”
http://1470.net/api/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
http://blog.goo.ne.jp/XMLRPC could not be pinged. Error message: “transport error - HTTP status code was not 200”

[bluemead]

Hi,

I have the same problem too.

The same sites have not pinged and show the same error code as bigSmile, with the exception of

http://ping.bitacoras.com could not be pinged. Error message: “parse error. not well formed”

This pinged successfully for me, so I have 7 pinging out of 15 on each of my 3 sites. All my error messages are

“transport error - HTTP status code was not 200”

My sites are set up on seperate domains, not in folders

Tricia

[bluemead]

Hi ,
I am stilll seeing the same results as BigSmile. I would like to know if this is normal or if there is something wrong somewhere that I could correct.
Any help from more knowledgeable people than I would be appreciated.

Thanks,
Tricia

[Nemo]

Hello Fellow 90DCers:
I am getting the same problem with "Smart Update Pinger". I started using www.Pingoat.com instead.

[golfer57]

Hello,

I am glad that you brought that to my attention. I am having the same problems as the rest of you guys. Most of the pings are not going through. Same error also:
02/22/07 08:04:55 - http://xmlrpc.blogg.de could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:04:55 - http://1470.net/api/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:04:55 - http://bblog.com/ping.php was successfully pinged (extended format)
02/22/07 08:04:56 - http://blog.goo.ne.jp/XMLRPC could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:06:43 Pinging services (new post: “Burberry Dog Collar - Fashion Statement for Pooches”) ...
02/22/07 08:06:43 - http://rpc.pingomatic.com was successfully pinged (extended format)
02/22/07 08:06:52 - http://ping.weblogs.se/ could not be pinged. Error message: “transport error - could not open socket: 0 Success”
02/22/07 08:06:58 - http://blogmatcher.com/u.php could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
02/22/07 08:06:58 - http://coreblog.org/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:06:59 - http://www.blogpeople.net/servlet/weblogUpdates was successfully pinged (extended format)
02/22/07 08:06:59 - http://bulkfeeds.net/rpc was successfully pinged
02/22/07 08:07:05 - http://trackback.bakeinu.jp/bakeping.php could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
02/22/07 08:07:06 - http://ping.myblog.jp was successfully pinged (extended format)
02/22/07 08:07:07 - http://ping.bitacoras.com could not be pinged. Error message: “parse error. not well formed”
02/22/07 08:07:07 - http://ping.bloggers.jp/rpc/ was successfully pinged
02/22/07 08:07:08 - http://ping.blogmura.jp/rpc/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:07:08 - http://xmlrpc.blogg.de could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:07:09 - http://1470.net/api/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
02/22/07 08:07:09 - http://bblog.com/ping.php was successfully pinged (extended format)
02/22/07 08:07:09 - http://blog.goo.ne.jp/XMLRPC could not be pinged. Error message: “transport error - HTTP status code was not 200”

I sure would think this is not normal...

Steve