[outages] Level3 IPv4 and IPv6 sessions bouncing in Denver, CO

[Frank Bulk]

Access to ipv6.level3.com came up minutes after I sent the message, at 5:32
pm Central.

 

>From the complete trace I see that the next hop after Kansas City is Denver.

 

nagios:/home/fbulk# tcptraceroute6 ipv6.level3.com

traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from
xxxxxxxxx, port 80, from port 39309, 30 hops max, 60 bytes packets

1  router-core.mtcnet.net (2607:fe28:0:1000::1)  0.253 ms  0.317 ms  0.192
ms

2  sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197)  0.192 ms  0.139 ms  0.135
ms

3  v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1)  5.526 ms  5.508
ms  5.488 ms

4  v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1)  9.829 ms  9.606
ms  9.635 ms

5  v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1)  10.934 ms  10.868 ms
10.864 ms

6  te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d)  17.140 ms
17.085 ms  17.168 ms

7  vl-4062.car2.Denver1.Level3.net (2001:1900:4:1::382)  30.076 ms  30.091
ms  30.036 ms

8  vl-51.car1.Denver1.Level3.net (2001:1900:13:1::3)  35.225 ms  39.585 ms
30.033 ms

9  Level3-MOSS.vl-956.car1.Denver1.Level3.net (2001:1900:4:2::fa)  30.552 ms
30.699 ms  30.779 ms

10  2001:1900:2018:f000:1:0:1:202 (2001:1900:2018:f000:1:0:1:202)  31.697 ms
31.685 ms  31.453 ms

11  ipv6.test.Level3.com (2001:1900:2018:3000::105)  32.317 ms [open]
32.400 ms  31.888 ms

nagios:/home/fbulk#

 

Frank

 

 

From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
Behalf Of Frank Bulk
Sent: Friday, October 05, 2012 5:30 PM
To: 'Chris Stone'; outages at outages.org
Subject: Re: [outages] Level3 IPv4 and IPv6 sessions bouncing in Denver, CO

 

I've not been able to access ipv6.level3.com since 4:11 pm Central . gets
stuck in Kansas

 

nagios:/home/fbulk# tcptraceroute6 ipv6.level3.com

traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from xxxxxxx,
port 80, from port 43472, 30 hops max, 60 bytes packets

1  router-core.mtcnet.net (2607:fe28:0:1000::1)  0.328 ms  0.302 ms  0.254
ms

2  sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197)  0.312 ms  0.131 ms  0.105
ms

3  v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1)  5.529 ms  5.545
ms  5.478 ms

4  v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1)  9.515 ms
10.254 ms  9.524 ms

5  v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1)  10.914 ms  11.119 ms
10.884 ms

6  te-3-3.car2.KansasCity1.Level3.net (2001:1900:2100::e2d)  17.358 ms
17.101 ms  17.128 ms

7  * * *

8  * * *

9  * * *

 

Frank

 

From: outages-bounces at outages.org <mailto:outages-bounces at outages.org>
[mailto:outages-bounces at outages.org] On Behalf Of Chris Stone
Sent: Friday, October 05, 2012 5:08 PM
To: outages at outages.org <mailto:outages at outages.org> 
Subject: [outages] Level3 IPv4 and IPv6 sessions bouncing in Denver, CO

 

Seeing my Level3 BGP sessions bouncing since 15:13:48 MDT and tracing in
from a CenturyLink circuit, dies with lots of packetloss on the 2nd to last
hop. Have ticket open with Level3 - waiting to hear something back.

HOST: orion.axint.net             Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 10.10.100.1                0.0%    50    0.5   0.5   0.4   0.7   0.0
  2.|-- 207.225.112.1              0.0%    50   41.0  50.0  39.4 181.7  27.6
  3.|-- 71.217.188.1               0.0%    50   39.9  41.5  39.3  87.4   6.8
  4.|-- 67.14.24.118               0.0%    50   40.7  44.4  39.7 100.5  12.0
  5.|-- 63.146.26.134              0.0%    50   59.6  60.8  58.7  92.8   5.3
  6.|-- 4.69.147.67               86.0%    50   84.2 277.0  73.0 1084. 366.3
  7.|-- ???                       100.0    50    0.0   0.0   0.0   0.0   0.0

Anyone else seeing L3 problems in Denver?


Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20121005/24f00bc5/attachment.htm>