[speed/latency] Interpretting a tracert in Verizon Online DSL http://www.dslreports.com/forum/r20450826 en Wed, 09 Jul 2008 01:23:55 EDT Wed, 09 Jul 2008 01:23:55 EDT Re: [speed/latency] Interpretting a tracert http://www.dslreports.com/forum/remark,20455271 NormanS :
said by AmyC See Profile :

The end IP is not pingable (webex.com). Does this just mean I'm hitting a bad router out there?
Not necessarily. Could just mean that the destination isn't responsive to ICMP. OTOH, trace route from my IP connection dies in a different manner than yours:
Level 3 performs the same function as MCI Communications Services. I can't check upstream adjacencies any more (the old web tool doesn't work; I haven't foud a replacement), so I don't know where either Level 3, or MCI come into play.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum]]> http://www.dslreports.com/forum/remark,20455271 Fri, 09 May 2008 05:44:48 EDT Re: [speed/latency] Interpretting a tracert http://www.dslreports.com/forum/remark,20452285 Smith6612 : It appears to be some sort of routing issue with Verizon, with either a peer being down or something else. When I run a trace route from my DSL connection from Verizon, it times out after hop 8 at the IP address of 152.63.36.53. This IP, according to WHOIS is owned by "MCI Communications Services, Inc. d/b/a Verizon Business ." So yeah, same problem here when I trace the server in your trace route from here. Don't know what to tell you here really...]]> http://www.dslreports.com/forum/remark,20452285 Thu, 08 May 2008 15:31:11 EDT Re: [speed/latency] Interpretting a tracert http://www.dslreports.com/forum/remark,20451463 Bytebender : Well, when I do a tracert to 64.68.97.165 ,
I hit 152.63.36.65 on hop 12 and then
hop 13 is webex-iad-gw.customer.alter.net at 65.207.89.50 and that is the last hop.
And 64.68.97.165 is not pingable.
Hope that helps some.]]> http://www.dslreports.com/forum/remark,20451463 Thu, 08 May 2008 12:43:22 EDT [speed/latency] Interpretting a tracert http://www.dslreports.com/forum/remark,20450826 AmyC : Hi. I have a weekly meeting using webex.com. every time we connect with, there is an awful connection on my end.

The Webex support states to do a tracert and look for latency. When we do the tracert, it fails at hop 9 every time and never is able to get beyond that after 30 hops.

The last IP it is able to get (hop 8) is an MCI/Verizon IP.

The end IP is not pingable (webex.com). Does this just mean I'm hitting a bad router out there?

Thanks!
webx.txt 3,084 bytes
tracert to webx and dslreports
]]> http://www.dslreports.com/forum/remark,20450826 Thu, 08 May 2008 10:48:24 EDT