dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
13
share rss forum feed


DrDrew
That others may surf
Premium
join:2009-01-28
SoCal
kudos:15
reply to depster

Re: [Speed] Congested Comcast Peering with Akamai, Google in Mid

said by depster:

It may be that your local router is being upgraded... in your first post Hop 3 indicated a 'te' interface.

When I just tracerouted to it now, it's showing as a 'xe' interface.

  3    20 ms    10 ms    10 ms  96.120.41.137
  4    12 ms     7 ms     7 ms  xe-8-2-0-sur01.grandrapids.mi.michigan.comcast.net [68.86.140.185]
  5    17 ms    19 ms    27 ms  te-0-2-0-4-ar01.taylor.mi.michigan.comcast.net [69.139.254.29]
  6    18 ms    17 ms    19 ms  xe-7-3-0-sur01.wannarbor.mi.michigan.comcast.net [68.85.218.201]
 

It's a different interface of the same router. OP's being from the edge of the network inbound, yours being from the core of the network outbound.
--
Two is one, one is none. If it's important, back it up... Somethimes 99.999% availability isn't even good enough.

johnnn

join:2007-01-25
Ypsilanti, MI

DrDrew is right. When I do tracerts *to* the edge they travel through an xe interface.