Anyone noticing any odd latency/bandwidth congestion going on in Seattle?

[bruns at 2mbit.com (Brielle)]

Hi all,

I've suddenly started showing high latency in Seattle off of CenturyLink 
in Boise going to Comcast in Denver.

Boise fiber to Denver...

traceroute to 50.239.215.xxx (50.239.215.xxx), 30 hops max, 60 byte packets
<trimmed>
  4  sea-brdr-02.inet.qwest.net (67.14.41.194)  12.394 ms  12.348 ms 
12.369 ms
  5  be-203-pe02.seattle.wa.ibone.comcast.net (96.87.10.117)  109.073 ms 
  109.530 ms  109.476 ms
  6  be-10847-cr01.seattle.wa.ibone.comcast.net (68.86.86.225)  110.906 
ms  111.427 ms  110.642 ms
  7  be-10820-cr01.champa.co.ibone.comcast.net (68.86.84.206)  125.245 
ms  126.605 ms  126.492 ms
  8  68.86.92.130 (68.86.92.130)  124.478 ms  124.533 ms  124.518 ms
  9  ae-1-rur02.wheatridge.co.denver.comcast.net (162.151.51.18) 
125.846 ms  126.010 ms  126.353 ms
10  ae-11-sur02.wheatridge.co.denver.comcast.net (162.151.51.146) 
125.630 ms  125.480 ms  125.397 ms
11  * * *
12  * * *

Reverse path from Denver Comcast to Boise CenturyLink...

traceroute to xxxxxxxxxxxxx (205.xxx.xx.xx), 30 hops max, 38 byte packets
  <trimmed>
  6  be-12176-pe02.910fifteenth.co.ibone.comcast.net (68.86.83.94) 
0.916 ms  0.983 ms  1.021 ms
  7  dvr3-brdr-01.inet.qwest.net (72.164.247.149)  0.864 ms  8.534 ms 
0.805 ms
  8  *  *  *
  9  63-224-242-xx.dia.static.qwest.net (63.224.242.xx)  125.355 ms 
125.681 ms  125.404 ms
10  63.147.164.xx (63.147.164.xx)  125.006 ms  125.590 ms  125.817 ms
11  *  *  *
12  *  *  *


I've got two CL fiber connections here in Boise - one with BGP for my 
own block, the other with a CL provided IP block.  Both showing same 
results.

Also have a CL fiber connection in Cheyenne, and it does not show any 
issues going to Boise or Denver.

Are we still seeing after-effects from the gaming thing last night?

-- 
Brielle Bruns
The Summit Open Source Development Group
http://www.sosdg.org    /     http://www.ahbl.org