AmyC
join:2004-03-25
Hermitage, PA
 ·Verizon Online DSL
edit:
May 8th, @11:17AM
|  [speed/latency] Interpretting a tracert
 webx.txt 3,084 bytes
tracert to webx and dslreports |
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! |
|
Bytebender
Bytebender
join:2008-02-12
Canada | 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. |
|
Smith6612
Premium
join:2008-02-01
united state
·Verizon Online DSL
·FrontierNet Intern..
edit:
May 8th, @03:31PM
| reply to AmyC
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... |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| reply to AmyC
said by AmyC  :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 |
|
