[KingRedOnion]

cheers kaktusan, i appreciate your input.

However - i know the error your talking about as i do run blog directories from this ip, but my recip checker runs locally on my personal pc. As a result, I have seen when thumblogger bans my ip.

This is different, this is that my server literally cannot ping thumblogger.com.

EXCEPT - for about 10 seconds last night, when it did start working then stopped again.

-bash-2.05b$ ping thumblogger.com
PING thumblogger.com (74.86.60.91): 56 data bytes
c64 bytes from 74.86.60.91: icmp_seq=11178 ttl=52 time=46.058 ms
64 bytes from 74.86.60.91: icmp_seq=11179 ttl=52 time=46.522 ms
64 bytes from 74.86.60.91: icmp_seq=11180 ttl=52 time=47.786 ms
64 bytes from 74.86.60.91: icmp_seq=11181 ttl=52 time=47.114 ms
64 bytes from 74.86.60.91: icmp_seq=11182 ttl=52 time=45.988 ms
64 bytes from 74.86.60.91: icmp_seq=11183 ttl=52 time=46.403 ms
64 bytes from 74.86.60.91: icmp_seq=11184 ttl=52 time=45.901 ms
64 bytes from 74.86.60.91: icmp_seq=11185 ttl=52 time=46.290 ms
^C
--- thumblogger.com ping statistics ---
30928 packets transmitted, 8 packets received, 99% packet loss
round-trip min/avg/max/stddev = 45.901/46.508/47.786/0.602 ms


----

my host (xxxhostit) replied with:

as you can see when you look at the bit that says "icmp_seq" those pings all occurred one after the other and the ping times were very good.
This indicates to me that someone opened the block for a few moments
You have to ask "dal01.dallas-datacenter.com" why they aren't letting your ping through


but i do not know who dallas-datacenter.com is