Ticket ID: SIXXS #11837513 Ticket Status: Remote Problem PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
connectivity from usqas01, uschi02 to Linode Atlanta
Shadow Hawkins on Thursday, 19 June 2014 18:02:04
Since about 5:15PM EDT yesterday, connectivity from both usqas01 (on work tunnel BCU5-SIXXS/T149373) and uschi02 (on home tunnel BCV6-SIXXS/T147933) to Linode Atlanta appears to be out.
From work to Linode:
bcoleman@ads7:~$ mtr -6 -r lns1.accelerateddesign.com
HOST: ads7 Loss% Snt Last Avg Best Wrst StDev
1.|-- 2001:4830:1600:4eb::1 0.0% 10 26.3 27.0 26.2 27.8 0.5
2.|-- sixxs-asbnva-gw.customer. 0.0% 10 26.9 27.6 26.0 36.2 3.0
3.|-- iad0-b0-ge2.hotnic.net 0.0% 10 26.5 27.8 26.3 36.7 3.2
4.|-- equinix6-was.ip.tiscali.n 0.0% 10 27.2 28.1 27.1 31.4 1.3
5.|-- xe-11-1-1.mia10.ip6.tinet 0.0% 10 62.1 59.3 55.9 67.3 4.3
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- mia12.ip6.tinet.net 0.0% 10 57.2 59.5 56.8 67.8 4.2
8.|-- so-10-1-0.was14.ip6.tinet 0.0% 10 72.3 77.3 70.8 90.9 8.4
9.|-- lo0.cr1.atl1.us.nlayer.ne 0.0% 10 63.3 56.8 54.8 63.3 2.9
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
and Linode to work:
bcoleman@lns1:~$ mtr -6 -r ads7.ln.accelerateddesign.com
Start: Thu Jun 19 13:42:53 2014
HOST: lns1 Loss% Snt Last Avg Best Wrst StDev
1.|-- 2600:3c02::8678:acff:fe5a 0.0% 10 0.7 0.7 0.6 0.7 0.0
2.|-- 2604:b900:1:1::1 0.0% 10 0.8 7.9 0.5 60.1 18.6
3.|-- 2400:8800:5f02:3::1 0.0% 10 0.9 1.0 0.8 1.5 0.0
4.|-- ibr01-ve96.asbn01.occaid. 10.0% 10 19.2 18.8 18.1 20.0 0.4
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
From home to Linode:
oloryn@fornost:~ mtr -6 -r lns1.accelerateddesign.com
Start: Thu Jun 19 13:44:39 2014
HOST: fornost Loss% Snt Last Avg Best Wrst StDev
1.|-- gw-1631.chi-02.us.sixxs.n 0.0% 10 50.4 35.8 33.1 50.4 5.2
2.|-- unassigned.v6.your.org 0.0% 10 33.8 33.9 32.4 35.4 0.8
3.|-- sixxs.ge-0.0.0-30.core1.c 0.0% 10 33.5 39.5 33.2 86.3 16.5
4.|-- ibx-chi.ip6.tiscali.net 0.0% 10 34.6 35.4 34.6 36.4 0.0
5.|-- 2001:668:0:2:ffff:0:8d88: 0.0% 10 95.1 95.8 93.2 108.3 4.4
6.|-- gtt-gw.ip6.tinet 0.0% 10 90.8 91.5 90.4 92.5 0.5
7.|-- mia12.ip6.tinet.net 0.0% 10 94.6 96.3 94.6 103.2 2.6
8.|-- so-10-1-0.was14.ip6.tinet 0.0% 10 95.5 96.3 95.1 102.3 2.0
9.|-- lo0.cr1.atl1.us.nlayer.ne 0.0% 10 78.9 81.4 78.4 89.7 4.1
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
and Linode to home:
bcoleman@lns1:~$ mtr -6 -r fornost.benshome.net
Start: Thu Jun 19 13:46:44 2014
HOST: lns1 Loss% Snt Last Avg Best Wrst StDev
1.|-- 2600:3c02::8678:acff:fe5a 0.0% 10 0.7 2.2 0.7 9.4 2.9
2.|-- 2604:b900:1:1::1 0.0% 10 0.9 8.6 0.5 55.4 17.9
3.|-- xe-8-2-3.edge4.Atlanta2.L 0.0% 10 0.7 0.6 0.5 0.7 0.0
4.|-- vl-51.car2.Atlanta2.Level 0.0% 10 0.8 0.9 0.8 1.2 0.0
5.|-- vl-4061.car2.Chicago1.Lev 0.0% 10 19.8 73.0 19.8 276.3 78.5
6.|-- vl-4062.edge2.Chicago2.Le 0.0% 10 19.6 20.2 19.6 24.8 1.5
7.|-- vl-52.ear1.Chicago2.Level 60.0% 10 6140. 3795. 2942. 6140. 1564.4
8.|-- xe-2-0-0.cr2.ord6.scnet.n 0.0% 10 20.6 20.7 20.6 20.8 0.0
9.|-- ae2-72.ar1.ord6.scnet.net 0.0% 10 20.4 20.9 20.3 26.2 1.8
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
I do know that Linode had a connectivity problem yesterday between their Atlanta and Newark locations that involved a problem with nlayer. Linode knows about this problem, but suggested that it would not hurt to have the other ends pushing on nlayer, also (if the problem is indeed at nlayer).
State change: remoteproblem
Jeroen Massar on Thursday, 19 June 2014 18:53:25
The state of this ticket has been changed to remoteproblem
connectivity from usqas01, uschi02 to Linode Atlanta
Jeroen Massar on Thursday, 19 June 2014 18:54:22
Can't reach that destination from a variety of other PoPs with traces ending remotely, hence, a remote problem that is out of our purview to resolve.
10 vl-4081.edge2.washington1.level3.net 278.847 ms 283.106 ms
vl-4083.edge2.washington1.level3.net 279.863 ms
11 vl-4040.car1.atlanta2.level3.net 293.771 ms 294.918 ms 292.979 ms
12 vl-52.edge4.atlanta2.level3.net 295.205 ms 292.395 ms 292.823 ms
13 giglinx-inc.edge4.atlanta2.level3.net 397.757 ms 921.949 ms 346.668 ms
14 2604:b900:1:1::2 296.110 ms 296.769 ms 292.023 ms
15 * * *
You'll have to contact Linode, nothing we can do about this.
Posting is only allowed when you are logged in. |