Quote:
Originally Posted by Patrick  Oops, I'm on Time Warner, not Cox. Appears to be the same routing, dallas, denver, chicago.. Is this the cause of my slowness in loading pages? Any corrections possible? |
The best thing to do is run a tracert to nloc.net and post it here and then share the results with your ISP
With enough tracerts I can share them with the datacenter that hosts the server BUT one user with slow tracert ONCE isnt enough to convince them of anything
for contrast here is the tracrt from my PC in dallas
C:\WINDOWS\system32>tracert nloc.net
Tracing route to nloc.net [208.100.8.12]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 2 ms 1 ms 1 ms 10.33.34.6
3 1 ms 1 ms 1 ms P0-3.LCR-03.DLLSTX.verizon-gni.net [130.81.48.12
0]
4 2 ms 2 ms 2 ms 130.81.29.180
5 3 ms 3 ms 3 ms 0.so-1-3-0.XT3.DFW9.ALTER.NET [152.63.0.25]
6 28 ms 28 ms 28 ms 0.so-6-0-0.XL1.CHI13.ALTER.NET [152.63.70.101]
7 27 ms 27 ms 27 ms POS6-0.GW1.CHI13.ALTER.NET [152.63.69.177]
8 29 ms 28 ms 28 ms wbsconnect-gw.customer.alter.net [65.207.236.126
]
9 28 ms 28 ms 28 ms web.nloc.net [208.100.8.12]
The first 2 hops are my router and my FIOS box on the side of the house - so they really dont count - After that there are 7 hops to the server and all the hops are under 30ms - That means that my connection to the server is FLYING and the server is flying.
I know that some of you are seeing slower response but trust me when I tell you its NOT the server - its the internet
post enough tracerts here and contact your ISPs and we can get this corrected - I hope