Da poco ho installato su vari blog con piattaforma WordPress un plugin che si chiama MaxBlogPress Ping Optimizer 1.5

Gestisce in maniera più accorta il servizio incluso in WP, inviando il ping solo quando effettivamente il contenuto è pubblicato. E non anche quando il post viene modificato o programmato nel tempo.
Questo plugin genera anche un log.

A parte pingomatic molti altri servizi sembrano non rispondere. Dove posso trovare una lista di servizi sicuramente attivi?
Vi incollo l'ultimo log prodotto

codice:
- http://rpc.pingomatic.com/ was successfully pinged (extended format)
    - http://api.feedster.com/ping could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
    - http://api.moreover.com/ping could not be pinged. Error message: “parse error. not well formed”
    - http://api.my.yahoo.com/rss/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://blogsearch.google.com/ping/RPC2 was successfully pinged (extended format)
    - http://ping.amagle.com/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://ping.bitacoras.com could not be pinged. Error message: “El ping no es válido porque tu bitácora no figura en el directorio de bitacoras.com, pero puedes darte de alta manualmente en http://bitacoras.com. Gracias por interesarte.”
    - http://ping.blo.gs/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://ping.feedburner.com was successfully pinged (extended format)
    - http://ping.rootblog.com/rpc.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://ping.syndic8.com/xmlrpc.php was successfully pinged (extended format)
    - http://ping.weblogalot.com/rpc.php was successfully pinged (extended format)
    - http://rcs.datashed.net/RPC2/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://rpc.blogbuzzmachine.com/RPC2 could not be pinged. Error message: “transport error - could not open socket: 0 Success”
    - http://rpc.blogrolling.com/pinger/ could not be pinged. Error message: “parse error. not well formed”
    - http://rpc.icerocket.com:10080/ could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
    - http://rpc.newsgator.com/ could not be pinged. Error message: “transport error - could not open socket: 0 Success”
    - http://rpc.technorati.com/rpc/ping was successfully pinged (extended format)
    - http://rpc.weblogs.com/RPC2 was successfully pinged (extended format)
    - http://topicexchange.com/RPC2 was successfully pinged (extended format)
    - http://www.blogdigger.com/RPC2 was successfully pinged
    - http://www.blogoole.com/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.blogoon.net/ping/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.blogsnow.com/ping could not be pinged. Error message: “parse error. not well formed”
    - http://www.blogstreet.com/xrbin/xmlrpc.cgi could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.lasermemory.com/lsrpc/ could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.newsisfree.com/RPCCloud could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.popdex.com/addsite.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.snipsnap.org/RPC2 could not be pinged. Error message: “transport error - HTTP status code was not 200”
    - http://www.wasalive.com/ping/ was successfully pinged (extended format)
    - http://www.weblogues.com/RPC/ could not be pinged. Error message: “transport error - HTTP status code was not 200”