[programmergeek]

ok I am on this site every day and it goes up and dow I get time out errors. I know that is not new but this may help. I did a ping of your site via ip and dns when it was going up and down. It appears the DNS is resolving even when the site is down so the DNS server is ok. but I am getting time out on the connection to your server. Is the DNS server and the server that hosts your site at the same place? do they have a bandwith limit? Here is what I got:

hummm, can't get image uploaded. e mail me and I will send you what I get if you need it.

Still the best RSWarrior site out there.

 

[carknee]

OK...
I noticed it has been horrible too!

Anyone who is computer/net savy, please email me a POST a traceroute and/or a ping to the site. I will then forward this info to my host.

[edit]email deleted[/edit]

Please post the info here, and I will give this link to the hosting co!

Thanks,
CarKnee

[edit by carknee @ 11:23]

 

[Cult_of_Speed]

Tracing route to www.rswarrior.com [207.202.0.127]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 172.16.10.1
2 1 ms 1 ms 1 ms 209.149.95.121
3 4 ms 4 ms 4 ms 172.18.211.89
4 13 ms 4 ms 4 ms 205.152.151.184
5 11 ms 11 ms 11 ms 500.POS2-1.GW8.ATL5.ALTER.NET [157.130.74.109]
6 11 ms 11 ms 11 ms 505.at-6-0-0.XL4.ATL5.ALTER.NET [152.63.83.174]

7 12 ms 11 ms 11 ms 0.so-2-1-0.TL2.ATL5.ALTER.NET [152.63.85.229]
8 33 ms 33 ms 33 ms 0.so-2-0-0.TL2.DFW9.ALTER.NET [152.63.0.2]
9 33 ms 34 ms 34 ms 0.so-7-0-0.XL2.DFW13.ALTER.NET [152.63.103.222]

10 34 ms 33 ms 33 ms POS7-0.GW2.DFW13.ALTER.NET [152.63.103.229]
11 33 ms 33 ms 33 ms wcgGigE-gw3.customer.alter.net [157.130.30.250]

12 34 ms 34 ms 34 ms dllstx1wcx2-oc48.wcg.net [64.200.110.81]
13 51 ms 51 ms 52 ms 64.200.232.126
14 52 ms 52 ms 51 ms hrndva1wcx2-oc48.wcg.net [64.200.95.73]
15 53 ms 53 ms 52 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
16 51 ms 52 ms 51 ms nycmny2wcx1-oc48.wcg.net [64.200.87.62]
17 52 ms 52 ms 52 ms nycmny2wcx1-winstar-pos.wcg.net [64.200.86.42]
18 254 ms 123 ms 271 ms 65.36.83.254
19 53 ms 53 ms 53 ms cust-11-feth-0-0.nyc.idt.net [169.132.120.252]
20 63 ms 90 ms 183 ms 206.20.153.118
21 169 ms 128 ms 175 ms 207.202.0.127

Trace complete.


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),

C:\Documents and Settings\smitht&gt/emoticons/emotion-4.gifing 207.202.0.127

Pinging 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),

C:\Documents and Settings\smitht&gt/emoticons/emotion-4.gifing www.yahoo.com

Pinging www.yahoo.akadns.net [64.58.76.222] with 32 bytes of data:

Reply from 64.58.76.222: bytes=32 time=30ms TTL=48
Reply from 64.58.76.222: bytes=32 time=30ms TTL=48
Reply from 64.58.76.222: bytes=32 time=31ms TTL=48
Reply from 64.58.76.222: bytes=32 time=30ms TTL=48

Ping statistics for 64.58.76.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 31ms, Average = 30ms

 

[carknee]

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

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 20 ms 10.27.0.1
2 10 ms 30 ms 10 ms dstswr2-vl2.rh.stjmny.cv.net [167.206.39.162]
3 10 ms 10 ms 70 ms opti39-133.nassau.cv.net [167.206.39.133]
4 20 ms 30 ms <10 ms r1-srp1-0.cr.hcvlny.cv.net [167.206.12.38]
5 10 ms 20 ms 10 ms r2-srp1-0.wan.hcvlny.cv.net [167.206.12.99]
6 20 ms 30 ms 10 ms r1-srp5-0.wan.hcvlny.cv.net [167.206.12.147]
7 20 ms 10 ms 10 ms iar3-so-3-2-0.NewYork.cw.net [208.173.135.145]
8 10 ms 10 ms 10 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
9 10 ms 10 ms 70 ms dcr1-so-6-1-0.NewYork.cw.net [206.24.207.53]
10 10 ms 10 ms 10 ms agr3-so-0-0-0.NewYork.cw.net [206.24.207.58]
11 30 ms 30 ms 30 ms acr2-loopback.Chicago.cw.net [208.172.2.62]
12 30 ms 30 ms 30 ms williams-communications-inc.Chicago.cw.net [208.
172.1.130]
13 60 ms 50 ms 50 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
14 50 ms 50 ms 70 ms nycmny2wcx1-oc48.wcg.net [64.200.87.66]
15 50 ms 51 ms 60 ms nycmny2wcx1-winstar-pos.wcg.net [64.200.86.42]
16 60 ms 60 ms 60 ms 65.36.83.254
17 50 ms 60 ms 50 ms cust-11-feth-0-0.nyc.idt.net [169.132.120.252]
18 100 ms 60 ms 70 ms 206.20.153.118
19 60 ms 90 ms 60 ms 207.202.0.127

Trace complete.

C:\>

C:\&gt/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=180ms TTL=108
Reply from 207.202.0.127: bytes=32 time=241ms TTL=108
Reply from 207.202.0.127: bytes=32 time=140ms TTL=108
Reply from 207.202.0.127: bytes=32 time=200ms TTL=108

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 241ms, Average = 190ms

C:\&gt/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=200ms TTL=108
Reply from 207.202.0.127: bytes=32 time=201ms TTL=108
Reply from 207.202.0.127: bytes=32 time=280ms TTL=108
Reply from 207.202.0.127: bytes=32 time=211ms TTL=108

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 280ms, Average = 223ms

 

[bljilek]

[email protected]:~$ tcptraceroute www.rswarrior.com
Selected device eth0, address 192.168.1.5, port 35249 for outgoing packets
Tracing the path to www.rswarrior.com (207.202.0.127) on TCP port 80, 30 hops max
1 192.168.1.1 (192.168.1.1) 0.388 ms 0.258 ms 0.251 ms
2 10.57.96.1 (10.57.96.1) 12.568 ms 6.960 ms 8.360 ms
3 24.31.193.136 (24.31.193.136) 14.895 ms 11.558 ms 8.646 ms
4 pop2-cha-P3-1.atdn.net (66.185.149.45) 15.572 ms 39.738 ms 12.649 ms
5 bb1-cha-P0-1.atdn.net (66.185.138.80) 12.212 ms 13.107 ms 15.032 ms
6 bb1-vie-P10-0.atdn.net (66.185.152.29) 23.195 ms 27.191 ms 21.953 ms
7 bb1-ash-P15-2.atdn.net (66.185.152.1/emoticons/emotion-11.gif 24.310 ms 41.902 ms 26.955 ms
8 pop2-ash-P0-0.atdn.net (66.185.139.209) 56.881 ms 26.084 ms 31.615 ms
9 WilliamsCommunications.atdn.net (66.185.141.250) 28.025 ms 27.677 ms 38.350 ms
10 hrndva1wcx3-oc48.wcg.net (64.200.95.117) 26.926 ms 82.630 ms 40.495 ms
11 hrndva1wcx2-oc48.wcg.net (64.200.95.73) 32.613 ms 34.075 ms 36.995 ms
12 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 35.726 ms 34.118 ms 34.965 ms
13 nycmny2wcx1-oc12.wcg.net (64.200.87.5/emoticons/emotion-11.gif 33.824 ms 33.782 ms 59.243 ms
14 nycmny2wcx1-winstar-pos.wcg.net (64.200.86.42) 32.348 ms 36.996 ms 32.307 ms
15 65.36.83.254 (65.36.83.254) 34.342 ms 35.845 ms 50.090 ms
16 cust-11-feth-0-0.nyc.idt.net (169.132.120.252) 34.201 ms 73.906 ms 39.836 ms
17 206.20.153.118 (206.20.153.11/emoticons/emotion-11.gif 115.141 ms 160.136 ms 157.320 ms
18 207.202.0.127 (207.202.0.127) [open] 44.664 ms 116.157 ms 54.732 ms

[email protected]:~$ ping www.rswarrior.com
PING www.rswarrior.com (207.202.0.127): 56 data bytes
64 bytes from 207.202.0.127: icmp_seq=6 ttl=110 time=81.8 ms
64 bytes from 207.202.0.127: icmp_seq=7 ttl=110 time=67.8 ms
64 bytes from 207.202.0.127: icmp_seq=8 ttl=110 time=54.7 ms
64 bytes from 207.202.0.127: icmp_seq=9 ttl=110 time=42.9 ms
64 bytes from 207.202.0.127: icmp_seq=10 ttl=110 time=205.9 ms
64 bytes from 207.202.0.127: icmp_seq=11 ttl=110 time=247.8 ms
64 bytes from 207.202.0.127: icmp_seq=12 ttl=110 time=306.4 ms
64 bytes from 207.202.0.127: icmp_seq=13 ttl=110 time=234.4 ms

--- www.rswarrior.com ping statistics ---
15 packets transmitted, 8 packets received, 46% packet loss
round-trip min/avg/max = 42.9/155.2/306.4 ms

 

[Cult_of_Speed]

Reply from 207.202.0.127: bytes=32 time=74ms TTL=107
Reply from 207.202.0.127: bytes=32 time=337ms TTL=107
Reply from 207.202.0.127: bytes=32 time=89ms TTL=107
Reply from 207.202.0.127: bytes=32 time=170ms TTL=107
Reply from 207.202.0.127: bytes=32 time=214ms TTL=107
Reply from 207.202.0.127: bytes=32 time=62ms TTL=107
Reply from 207.202.0.127: bytes=32 time=157ms TTL=107
Reply from 207.202.0.127: bytes=32 time=67ms TTL=107
Reply from 207.202.0.127: bytes=32 time=87ms TTL=107
Reply from 207.202.0.127: bytes=32 time=90ms TTL=107
Request timed out.
Request timed out.
Reply from 207.202.0.127: bytes=32 time=233ms TTL=107
Reply from 207.202.0.127: bytes=32 time=136ms TTL=107
Reply from 207.202.0.127: bytes=32 time=275ms TTL=107
Reply from 207.202.0.127: bytes=32 time=136ms TTL=107
Reply from 207.202.0.127: bytes=32 time=117ms TTL=107
Reply from 207.202.0.127: bytes=32 time=127ms TTL=107
Reply from 207.202.0.127: bytes=32 time=90ms TTL=107
Reply from 207.202.0.127: bytes=32 time=171ms TTL=107
Reply from 207.202.0.127: bytes=32 time=194ms TTL=107
Reply from 207.202.0.127: bytes=32 time=115ms TTL=107
Reply from 207.202.0.127: bytes=32 time=196ms TTL=107
Reply from 207.202.0.127: bytes=32 time=144ms TTL=107
Reply from 207.202.0.127: bytes=32 time=189ms TTL=107
Reply from 207.202.0.127: bytes=32 time=231ms TTL=107
Request timed out.
Reply from 207.202.0.127: bytes=32 time=116ms TTL=107
Reply from 207.202.0.127: bytes=32 time=97ms TTL=107
Reply from 207.202.0.127: bytes=32 time=196ms TTL=107
Reply from 207.202.0.127: bytes=32 time=278ms TTL=107
Reply from 207.202.0.127: bytes=32 time=240ms TTL=107
Reply from 207.202.0.127: bytes=32 time=186ms TTL=107
Reply from 207.202.0.127: bytes=32 time=267ms TTL=107
Reply from 207.202.0.127: bytes=32 time=211ms TTL=107
Reply from 207.202.0.127: bytes=32 time=283ms TTL=107
Reply from 207.202.0.127: bytes=32 time=208ms TTL=107
Reply from 207.202.0.127: bytes=32 time=177ms TTL=107
Reply from 207.202.0.127: bytes=32 time=157ms TTL=107
Reply from 207.202.0.127: bytes=32 time=196ms TTL=107
Reply from 207.202.0.127: bytes=32 time=232ms TTL=107
Request timed out.
Reply from 207.202.0.127: bytes=32 time=232ms TTL=107
Reply from 207.202.0.127: bytes=32 time=175ms TTL=107
Reply from 207.202.0.127: bytes=32 time=276ms TTL=107
Reply from 207.202.0.127: bytes=32 time=253ms TTL=107


Notice the time outs? And the pings I did earlier? There is some packet loss on the line. I would call the local telco or if you are renting space somewhere call the company and have them call local telco and request a line test.

My .02 cents

 

[bulldog]

--- www.rswarrior.com ping statistics ---
35 packets transmitted, 34 received, 2% loss, time 34323ms
rtt min/avg/max/mdev = 62.917/178.000/319.162/78.527 ms

[[email protected] root]# traceroute www.rswarrior.com
traceroute to www.rswarrior.com (207.202.0.127), 30 hops max, 38 byte packets
1 199.82.255.129 (199.82.255.129) 0.480 ms 0.414 ms 0.400 ms
2 199.82.255.65 (199.82.255.65) 0.993 ms 0.871 ms 0.761 ms
3 199.82.250.131 (199.82.250.131) 0.886 ms 0.653 ms 0.582 ms
4 146.18.69.2 (146.18.69.2) 20.481 ms 69.944 ms 3.808 ms
5 memi2erc02-a00.corp.fedex.com (146.18.136.2) 2.986 ms 1.911 ms 1.722 ms
6 146.18.70.4 (146.18.70.4) 4.561 ms 4.145 ms 4.177 ms
7 g3-corpnet.fw.fedex.com (199.81.77.71) 3.093 ms 3.472 ms 3.927 ms
8 memineti.network.fedex.com (199.81.192.90) 5.302 ms 4.839 ms 5.544 ms
9 500.serial2-8.gw5.stl3.alter.net (65.208.81.233) 16.979 ms 10.303 ms 16.868 ms
10 109.at-5-0-0.xl2.stl3.alter.net (152.63.67.166) 12.596 ms 16.038 ms 12.072 ms
11 0.so-1-0-0.tl2.stl3.alter.net (152.63.88.245) 12.239 ms 14.601 ms 14.888 ms
12 0.so-5-2-0.tl2.dfw9.alter.net (152.63.1.149) 30.756 ms 30.125 ms 28.973 ms
13 0.so-7-0-0.xl2.dfw13.alter.net (152.63.103.222) 29.650 ms 35.386 ms 33.581 ms
14 pos7-0.gw2.dfw13.alter.net (152.63.103.229) 30.037 ms 32.613 ms 28.459 ms
15 wcggige-gw3.customer.alter.net (157.130.30.250) 78.460 ms 75.875 ms 84.008 ms
16 dllstx1wcx2-oc48.wcg.net (64.200.110.81) 92.013 ms 89.814 ms 93.657 ms
17 64.200.232.126 (64.200.232.126) 101.129 ms 97.413 ms 102.514 ms
18 hrndva1wcx2-oc48.wcg.net (64.200.95.77) 103.785 ms 94.208 ms 93.512 ms
19 nycmny2wcx2-oc48.wcg.net (64.200.240.45) 96.562 ms 94.541 ms 93.918 ms
20 nycmny2wcx1-oc12.wcg.net (64.200.87.5/emoticons/emotion-11.gif 89.015 ms 83.522 ms 79.039 ms
21 nycmny2wcx1-winstar-pos.wcg.net (64.200.86.42) 82.599 ms 90.871 ms 83.041 ms
22 65.36.83.254 (65.36.83.254) 78.581 ms 126.274 ms 109.339 ms
23 cust-11-feth-0-0.nyc.idt.net (169.132.120.252) 120.168 ms 110.994 ms 107.719 ms
24 206.20.153.118 (206.20.153.11/emoticons/emotion-11.gif 224.739 ms 128.672 ms 124.498 ms
25 207.202.0.127 (207.202.0.127) 174.230 ms 155.553 ms 196.673 ms

 

[carknee]

They originally said that Winstar was having major packet loss, and I See that they are coming up on all the traces...

 

[islecruiser]

I guess im really stupid because I have no clue to what i'm looking at here.

 

[carknee]

This is a list of Traceroutes and Pings from the users computer to the web server. In laymans terms...

Traceroute:
A small piece of information is sent from the user to the web site. This piece of information will tell us where it has gone on its trip to the web server.

Ping:
A small piece of information is sent from the user to the web site. This piece of information will tell us how long it takes to get to the web server.

This information can help the web hosting company trouble shoot their network problems.

C

 

[EzGo_n]

Tracing route to www.rswarrior.com [207.202.0.127]
over a maximum of 30 hops:

1 14 ms 15 ms 15 ms HSE-Toronto-ppp186032.sympatico.ca [64.229.113.1]
2 160 ms 198 ms 203 ms dis27-toronto63-Vlan200.in.bellnexxia.net [64.230.244.130]
3 14 ms 15 ms 14 ms core3-toronto63-Gigabite4-1.in.bellnexxia.net [206.108.107.173]
4 24 ms 26 ms 25 ms core2-chicago23-pos0-0.in.bellnexxia.net [206.108.103.114]
5 25 ms 26 ms 25 ms bx1-chicago23-pos11-0.in.bellnexxia.net [206.108.103.125]
6 25 ms 25 ms 25 ms sl-gw31-chi-4-0.sprintlink.net [160.81.92.1]
7 26 ms 27 ms 26 ms sl-bb21-chi-4-0.sprintlink.net [144.232.26.29]
8 45 ms 46 ms 45 ms sl-bb21-fw-10-0.sprintlink.net [144.232.8.54]
9 45 ms 46 ms 44 ms sl-gw20-fw-9-0.sprintlink.net [144.232.11.130]
10 49 ms 54 ms 47 ms sl-williamscom-11-0.sprintlink.net [144.232.194.50]
11 65 ms 68 ms 66 ms 64.200.232.126
12 66 ms 66 ms 66 ms hrndva1wcx2-oc48.wcg.net [64.200.95.73]
13 69 ms 66 ms 64 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
14 68 ms 67 ms 66 ms nycmny2wcx1-oc12.wcg.net [64.200.87.58]
15 65 ms 66 ms 64 ms nycmny2wcx1-winstar-pos.wcg.net [64.200.86.42]
16 67 ms 66 ms 66 ms 65.36.83.254
17 66 ms 67 ms 69 ms cust-11-feth-0-0.nyc.idt.net [169.132.120.252]
18 77 ms 74 ms 74 ms 206.20.153.118
19 73 ms 75 ms 73 ms 207.202.0.127
Trace complete.

Pinging www.rswarrior.com [207.202.0.127] with 32 bytes of data:

Reply from 207.202.0.127: bytes=32 time=81ms TTL=116
Reply from 207.202.0.127: bytes=32 time=79ms TTL=116
Reply from 207.202.0.127: bytes=32 time=337ms TTL=116
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 = 337ms, Average = 165ms

 

[islecruiser]

Thanks carknee,I think i know what you mean.

 

[darkstar]

Yea, right IsleCruiser! How the **** do you understand all that crap? I'll stick to being dumb then rather putting myself through that kind of torture!

 

[programmergeek]

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:\&gt/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:\&gt/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:\&gt/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:\&gt/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:\&gt/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:\&gt/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:\&gt/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

 

[carknee]

10/30/02 9am
----------------
Tracing route to www.rswarrior.com [207.202.0.127]
over a maximum of 30 hops:

1 10 ms 10 ms 10 ms 10.27.0.1
2 10 ms 10 ms 10 ms dstswr2-vl2.rh.stjmny.cv.net [167.206.39.162]
3 601 ms 190 ms 20 ms opti39-133.nassau.cv.net [167.206.39.133]
4 11 ms 10 ms 10 ms r1-srp1-0.cr.hcvlny.cv.net [167.206.12.38]
5 10 ms 10 ms 20 ms r2-srp1-0.wan.hcvlny.cv.net [167.206.12.99]
6 10 ms 10 ms 10 ms r1-srp5-0.wan.hcvlny.cv.net [167.206.12.147]
7 10 ms 20 ms 10 ms iar3-so-3-2-0.NewYork.cw.net [208.173.135.145]
8 40 ms 40 ms 10 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
9 550 ms 211 ms 10 ms dcr1-so-6-1-0.NewYork.cw.net [206.24.207.53]
10 10 ms 10 ms 20 ms agr4-so-4-0-0.NewYork.cw.net [206.24.207.78]
11 20 ms 20 ms 30 ms acr1-loopback.Restonrst.cw.net [206.24.178.61]
12 20 ms 20 ms 20 ms iar1-loopback.Restonrst.cw.net [206.24.178.22]
13 40 ms 40 ms 40 ms williams-communications-inc.Restonrst.cw.net [20
8.173.155.26]
14 40 ms 30 ms 30 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
15 40 ms 50 ms 30 ms nycmny2wcx1-oc48.wcg.net [64.200.87.62]
16 30 ms 40 ms 30 ms nycmny2wcx1-winstar-pos.wcg.net [64.200.86.42]
17 130 ms 531 ms 330 ms 65.36.83.254
18 40 ms 40 ms 40 ms cust-11-feth-0-0.nyc.idt.net [169.132.120.252]
19 70 ms 60 ms 50 ms 206.20.153.118
20 60 ms 120 ms 50 ms 207.202.0.127

Trace complete.

 

[carknee]

Pinging www.rswarrior.com [207.202.0.127] with 32 bytes of data:

Reply from 207.202.0.127: bytes=32 time=140ms TTL=108
Reply from 207.202.0.127: bytes=32 time=90ms TTL=108
Reply from 207.202.0.127: bytes=32 time=180ms TTL=108
Reply from 207.202.0.127: bytes=32 time=210ms TTL=108

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 210ms, Average = 155ms

 

[carknee]

9:30 am
---------------
Tracing route to www.rswarrior.com [207.202.0.127]
over a maximum of 30 hops:


1 20 ms 10 ms 10 ms 10.27.0.1
2 10 ms <10 ms 10 ms dstswr2-vl2.rh.stjmny.cv.net [167.206.39.162]
3 10 ms 10 ms 30 ms opti39-133.nassau.cv.net [167.206.39.133]
4 10 ms 10 ms 20 ms r1-srp1-0.cr.hcvlny.cv.net [167.206.12.38]
5 20 ms 10 ms 20 ms r2-srp1-0.wan.hcvlny.cv.net [167.206.12.99]
6 10 ms 10 ms 10 ms r1-srp5-0.wan.hcvlny.cv.net [167.206.12.147]
7 20 ms 10 ms 10 ms iar3-so-3-2-0.NewYork.cw.net [208.173.135.145]
8 10 ms 20 ms 20 ms agr1-loopback.NewYork.cw.net [206.24.194.101]
9 10 ms 10 ms 30 ms dcr1-so-6-1-0.NewYork.cw.net [206.24.207.53]
10 10 ms 10 ms 30 ms agr4-so-4-0-0.NewYork.cw.net [206.24.207.78]
11 20 ms 20 ms 30 ms acr1-loopback.Restonrst.cw.net [206.24.178.61]
12 20 ms 30 ms 30 ms iar1-loopback.Restonrst.cw.net [206.24.178.22]
13 30 ms 60 ms 41 ms williams-communications-inc.Restonrst.cw.net [208.173.155.26]
14 40 ms * 40 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
15 50 ms 50 ms 40 ms nycmny2wcx1-oc48.wcg.net [64.200.87.62]
16 40 ms 30 ms 40 ms nycmny2wcx1-winstar-pos.wcg.net [64.200.86.42]
17 40 ms 40 ms 40 ms 65.36.83.254
18 40 ms 40 ms 40 ms cust-11-feth-0-0.nyc.idt.net [169.132.120.252]
19 60 ms 70 ms 70 ms 206.20.153.118
20 100 ms 60 ms 60 ms 207.202.0.127

Trace complete.

 

[carknee]

Pinging www.rswarrior.com [207.202.0.127] with 32 bytes of data:

Reply from 207.202.0.127: bytes=32 time=70ms TTL=108
Reply from 207.202.0.127: bytes=32 time=70ms TTL=108
Reply from 207.202.0.127: bytes=32 time=70ms TTL=108
Reply from 207.202.0.127: bytes=32 time=140ms TTL=108

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 140ms, Average = 87ms

 

[VikingWarrior]

Pinging 207.202.0.127 with 32 bytes of data:

Request timed out.
Reply from 207.202.0.127: bytes=32 time=29ms TTL=112
Reply from 207.202.0.127: bytes=32 time=89ms TTL=112
Reply from 207.202.0.127: bytes=32 time=155ms TTL=112

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 155ms, Average = 68ms

 

[VikingWarrior]

Pinging 207.202.0.127 with 32 bytes of data:

Request timed out.
Reply from 207.202.0.127: bytes=32 time=51ms TTL=112
Reply from 207.202.0.127: bytes=32 time=30ms TTL=112
Reply from 207.202.0.127: bytes=32 time=152ms TTL=112

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 152ms, Average = 58ms


Pinging 207.202.0.127 with 32 bytes of data:

Reply from 207.202.0.127: bytes=32 time=294ms TTL=112
Reply from 207.202.0.127: bytes=32 time=39ms TTL=112
Reply from 207.202.0.127: bytes=32 time=38ms TTL=112
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 = 38ms, Maximum = 294ms, Average = 92ms


Pinging 207.202.0.127 with 32 bytes of data:

Reply from 207.202.0.127: bytes=32 time=132ms TTL=112
Reply from 207.202.0.127: bytes=32 time=175ms TTL=112
Request timed out.
Reply from 207.202.0.127: bytes=32 time=38ms TTL=112

Ping statistics for 207.202.0.127:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss)
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 175ms, Average = 86ms