davidgibson opened this issue on Apr 19, 2006 · 32 posts
Khai posted Sat, 22 April 2006 at 8:13 PM
ok lets take this futher with Diagnostic Data:
Ping to www.renderosity.com :
C:Documents and SettingsKhai>ping www.renderosity.com
Pinging www.renderosity.com [66.18.106.204] with 32 bytes of data:
Reply from 66.18.106.204: bytes=32 time=98ms TTL=44
Reply from 66.18.106.204: bytes=32 time=164ms TTL=44
Reply from 66.18.106.204: bytes=32 time=165ms TTL=44
Reply from 66.18.106.204: bytes=32 time=98ms TTL=44
Ping statistics for 66.18.106.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 165ms, Average = 131ms
a good fast ping.
next a tracert
C:Documents and SettingsKhai>tracert www.renderosity.com
Tracing route to www.renderosity.com [66.18.106.204]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.2.1
2 59 ms 91 ms 87 ms 10.72.64.1
3 83 ms 185 ms 225 ms d226-3-81.home.cgocable.net [24.226.3.81]
4 172 ms 29 ms 54 ms g2-1-2.core01.yyz02.atlas.cogentco.com [38.112.2
40.137]
5 * * * Request timed out.
6 * 27 ms 39 ms v3492-mpd01.yyz01.atlas.cogentco.com [154.54.5.8
1]
7 22 ms 14 ms 24 ms g3-0-0-3491-core01.yyz01.atlas.cogentco.com [154
.54.5.77]
8 34 ms 30 ms 31 ms p13-0.core02.ord01.atlas.cogentco.com [66.28.4.2
13]
9 * 50 ms 33 ms v5.mpd01.ord01.atlas.cogentco.com [154.54.3.254]
10 49 ms 65 ms 108 ms v3498.mpd01.ord03.atlas.cogentco.com [154.54.5.2
]
11 143 ms 186 ms 202 ms g3-0-0-3490.core01.ord03.atlas.cogentco.com [154
.54.3.233]
12 154 ms 250 ms 162 ms 206.111.2.29
13 152 ms 75 ms 31 ms p5-0-0.RAR1.Chicago-IL.us.xo.net [65.106.6.133]
14 146 ms 167 ms 187 ms p6-0-0.RAR2.Washington-DC.us.xo.net [65.106.0.46
]
15 127 ms 181 ms 115 ms p6-0-0.RAR2.Atlanta-GA.us.xo.net [65.106.0.6]
16 296 ms 133 ms 83 ms p4-0-0.MAR2.Nashville-TN.us.xo.net [65.106.4.50]
17 132 ms 152 ms 198 ms p15-1.CHR1.Nashville-TN.us.xo.net [207.88.85.126
]
18 160 ms 69 ms 62 ms 66.238.242.46.ptr.us.xo.net [66.238.242.46]
19 168 ms 140 ms 153 ms cs01.bna2.rentech.net [66.18.99.72]
20 245 ms 136 ms 69 ms unk.bondware.com [66.18.106.204]
Trace complete.
while there's a timeout, still a reasonable trace time.
but..... page load time .... 18.995 seconds.... (the above trace (with timeout) took 6 seconds)
anyone wanna explain the disparity of 13 seconds?