- The part up to packetexchange.net is your internet provider.
- After packetexchange.net it is our web hosting company's network.
- A delay between your ISP and our provider's network might be the fault of either side.
- 'Request timed out' is nothing to worry about - it just means at one hop the server has a firewall the blocks a response.
- Timing numbers are three samples of the latency which are cumulative for each step.
- The final latency depends on distance, but over 100ms for the US should be ok.
- Unfortunately tracert does only latency and not throughput so it is hard to determine the bottlenecks.
So for you there is a lot of internal latency with comcast (32ms) and then the rest (50ms) is between comcast and our provider.
Compare with our tracert. Note it gets to the provider's network in 4ms rather than 80ms and the ISP delay is 4ms rather 32ms.
1 <1 ms <1 ms <1 ms x
2 <1 ms <1 ms <1 ms x
3 4 ms 3 ms 3 ms cr81.gr2ca.ip.att.net [12.122.154.74]
4 4 ms 3 ms 3 ms cr81.gr2ca.ip.att.net [12.122.154.74]
5 1 ms 1 ms 1 ms 12.122.154.101
6 1 ms 3 ms 3 ms 12.122.154.102
7 7 ms 7 ms 7 ms cr2.la2ca.ip.att.net [12.122.154.65]
8 5 ms 3 ms 3 ms ggr2.la2ca.ip.att.net [12.122.129.105]
9 16 ms 5 ms 4 ms 192.205.37.146
10 * * * Request timed out.
11 8 ms 3 ms 3 ms cr1.lax1.us.packetexchange.net [4.71.136.2]
12 3 ms 3 ms 3 ms csw3.lax1.inmotionhosting.com [198.46.92.2]
13 4 ms 4 ms 4 ms csw4.lax1.inmotionhosting.com [198.46.92.3]
14 3 ms 3 ms 3 ms csw1.lax1.inmotionhosting.com [198.46.92.26]
15 4 ms 4 ms 4 ms server.hondata.com [144.208.68.130]