Ok I am guessing here but it looks like it got to your provider, 207 and died. the trace also took several minutes to run, which makes me beleve that there server is taking to log to respond.
C:\>tracert
www.rswarrior.com
Tracing route to
www.rswarrior.com [207.202.0.127]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 10.250.0.1
2 <10 ms <10 ms <10 ms 172.23.253.252
3 <10 ms <10 ms <10 ms 205.246.211.220
4 <10 ms <10 ms <10 ms 208.240.192.129
5 <10 ms <10 ms <10 ms 137.39.7.181
6 <10 ms <10 ms <10 ms 152.63.24.206
7 63 ms 31 ms 16 ms 152.63.17.194
8 <10 ms <10 ms 16 ms 152.63.19.29
9 <10 ms <10 ms <10 ms 152.63.0.153
10 <10 ms 16 ms 15 ms 152.63.0.161
11 <10 ms 16 ms 16 ms 152.63.144.50
12 15 ms 16 ms 16 ms 152.63.34.250
13 47 ms 31 ms 16 ms 152.63.38.129
14 <10 ms 31 ms 16 ms 152.63.41.29
15 63 ms 140 ms 141 ms 157.130.30.246
16 109 ms 172 ms 94 ms 64.200.95.117
17 94 ms 47 ms 31 ms 64.200.95.73
18 343 ms 391 ms 594 ms 64.200.240.45
19 313 ms 406 ms 390 ms 64.200.87.62
20 250 ms 204 ms 187 ms 64.200.86.42
21 110 ms 78 ms 31 ms 65.36.83.254
22 203 ms 125 ms 187 ms 169.132.120.252
23 469 ms 235 ms 359 ms 206.20.153.118
24 * * * Request timed out.
25 * * * Request timed out.
26 * 172 ms 125 ms 207.202.0.127
Trace complete.
Also here are several pings. The pings are taking to long look at the times if they get through at all. The last one is my site which I run off of DSL in my basement that is what it should loiook like. There server is not responding fast enought or is overloaded.
I tried going after the IP directly and still timed out I think that would bypass there dns server. So I think the issue is with there web server. As opposed to there DNS server not resolving.
C:\>/emoticons/emotion-4.gifing
www.rswarrior.com
Pinging
www.rswarrior.com [207.202.0.127] with 32 bytes of data:
Reply from 207.202.0.127: bytes=32 time=344ms TTL=105
Reply from 207.202.0.127: bytes=32 time=47ms TTL=105
Reply from 207.202.0.127: bytes=32 time=172ms TTL=105
Reply from 207.202.0.127: bytes=32 time=78ms TTL=105
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 344ms, Average = 160ms
C:\>/emoticons/emotion-4.gifing
www.rswarrior.com
Pinging
www.rswarrior.com [207.202.0.127] with 32 bytes of data:
Reply from 207.202.0.127: bytes=32 time=79ms TTL=105
Reply from 207.202.0.127: bytes=32 time=235ms TTL=105
Reply from 207.202.0.127: bytes=32 time=125ms TTL=105
Request timed out.
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 235ms, Average = 109ms
C:\>/emoticons/emotion-4.gifing
www.rswarrior.com
Pinging
www.rswarrior.com [207.202.0.127] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>/emoticons/emotion-4.gifing
www.rswarrior.com
Pinging
www.rswarrior.com [207.202.0.127] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 207.202.0.127: bytes=32 time=16ms TTL=105
Reply from 207.202.0.127: bytes=32 time=47ms TTL=105
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 47ms, Average = 15ms
C:\>/emoticons/emotion-4.gifing 207.202.0.127
Pinging 207.202.0.127 with 32 bytes of data:
Reply from 207.202.0.127: bytes=32 time=172ms TTL=105
Reply from 207.202.0.127: bytes=32 time=203ms TTL=105
Reply from 207.202.0.127: bytes=32 time=125ms TTL=105
Reply from 207.202.0.127: bytes=32 time=203ms TTL=105
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 203ms, Average = 175ms
C:\>/emoticons/emotion-4.gifing 207.202.0.127
Pinging 207.202.0.127 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 207.202.0.127: bytes=32 time=125ms TTL=105
Reply from 207.202.0.127: bytes=32 time=172ms TTL=105
Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 172ms, Average = 74ms
C:\>
C:\>/emoticons/emotion-4.gifing
www.programmergeek.com
Pinging ns.programmergeek.com [64.81.197.144] with 32 bytes of data:
Reply from 64.81.197.144: bytes=32 time=31ms TTL=238
Reply from 64.81.197.144: bytes=32 time=31ms TTL=238
Reply from 64.81.197.144: bytes=32 time=32ms TTL=238
Reply from 64.81.197.144: bytes=32 time=32ms TTL=238
Ping statistics for 64.81.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms
