Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Seattle POP - Shaw Cable peering  (Read 1460 times)

mikeyur

  • Newbie
  • *
  • Posts: 2
Seattle POP - Shaw Cable peering
« on: July 11, 2014, 06:43:19 AM »

I noticed that my pings to the seattle pop are higher than what I'm used to seeing from Vancouver, typically 13-15ms but I've been seeing 40-60ms. Did a traceroute and it looks like I'm doing a loop through northern California and then back up to Seattle.

I'm with Shaw Cable (AS6327) and they peer at SIX.

It's not the end of the world if I have to deal with some extra latency, but thought I'd throw it out there anyways. Thanks.

Code: [Select]
traceroute to 216.218.226.238 (216.218.226.238), 64 hops max, 52 byte packets
 1  10.0.1.1 (10.0.1.1)  2.879 ms  0.780 ms  0.684 ms
 2  * * *
 3  rd3bb-tge0-8-2-0-1.vc.shawcable.net (64.59.148.129)  9.030 ms  12.281 ms  9.002 ms
 4  66.163.72.217 (66.163.72.217)  11.051 ms
    66.163.74.101 (66.163.74.101)  11.349 ms
    66.163.72.241 (66.163.72.241)  11.932 ms
 5  30gigabitethernet2-1.core1.pao1.he.net (198.32.176.20)  58.944 ms  51.218 ms  48.762 ms
 6  10ge3-1.core1.sjc2.he.net (72.52.92.70)  41.178 ms  39.438 ms  32.761 ms
 7  10ge12-1.core1.sea1.he.net (72.52.92.158)  34.149 ms  50.609 ms  48.754 ms
 8  tserv1.sea1.he.net (216.218.226.238)  41.320 ms  41.948 ms  46.194 ms
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Seattle POP - Shaw Cable peering
« Reply #1 on: July 11, 2014, 09:37:11 AM »

They peer with HE there, so for some reason they are preferring routes out of Palo Alto.

From lg.he.net, SIX peers:
Code: [Select]
  206.81.80.54      6327        ESTAB   19d 4h32m     1663        0        57042    0

Sounds like something for Shaw to fix.
Logged

mikeyur

  • Newbie
  • *
  • Posts: 2
Re: Seattle POP - Shaw Cable peering
« Reply #2 on: July 11, 2014, 08:40:57 PM »

They peer with HE there, so for some reason they are preferring routes out of Palo Alto.

From lg.he.net, SIX peers:
Code: [Select]
  206.81.80.54      6327        ESTAB   19d 4h32m     1663        0        57042    0

Sounds like something for Shaw to fix.

Thanks. I'll send them a message and see.
Logged