[aklug] Re: Alaska peering

Leif Sawyer wrote, on 6/8/2010 4:15 PM:
>> All that we still need is a GCI-MTA test, then ... and
>> preferably not from a Clearwire node, as the wireless
>> performance makes it hard to discern big changes in the hops.
>
> How about from behind my cablemodem?
>
> leif@gw:~$ tracepath 216.152.176.1
> 1: gw.denali.net (69.178.4.20) 0.474ms pmtu 1500
> 1: (CMTS - no ICMP support)
> 2: 81-188-165-209.gci.net (209.165.188.81) 21.349ms
> 3: 34-128-165-209.gci.net (209.165.128.34) 8.670ms
> 4: 9-128-165-209.gci.net (209.165.128.9) 10.749ms
> 5: 31-128-165-209.gci.net (209.165.128.31) 26.438ms
> 6: 198-168-165-209.static.gci.net (209.165.168.198) 22.689ms
> 7: 216.152.176.226 (216.152.176.226) 36.457ms asymm 8
> 8: ns1.mtaonline.net (216.152.176.1) 17.850ms !H
> Resume: pmtu 1500

Is there some other traffic going on that would make your third hop have a 21ms delay?

This looks like GCI and MTA are peering. There's not a big spike in between, and no obvious Seattle bump.

Royce
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jun 8 16:22:39 2010