HE having an (IPv6) problem?
Many IPv6 sites that I monitoring are repoting down ... the first few I checked are with HE: root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed... root@nagios:~/tmp#
Just started seeing ipv4 issues here, glad somebody else popped up on the list. Actually, it may have just resolved... On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org> wrote:
Many IPv6 sites that I monitoring are repoting down ... the first few I checked are with HE:
root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed... root@nagios:~/tmp#
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
For about 8 minutes, ending around 2:18.. Annnnd it just went down again... ----- 3 4 ms 3 ms 4 ms kcweb-209-153-68-1.static.ptr.kcweb.net [209.153.68.1] 4 6 ms 6 ms 6 ms 10.1.71.1 5 12 ms 7 ms 13 ms v234.core1.mci2.he.net [216.66.74.245] 6 9 ms 5 ms 15 ms 10ge4-3.core1.mci3.he.net [184.105.213.38] 7 * * * Request timed out. ----- On Mon, Jun 6, 2016 at 2:15 PM, Josh Reynolds <josh@kyneticwifi.com> wrote:
Just started seeing ipv4 issues here, glad somebody else popped up on the list.
Actually, it may have just resolved...
On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org> wrote:
Many IPv6 sites that I monitoring are repoting down ... the first few I checked are with HE:
root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed... root@nagios:~/tmp#
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
My NLNOG ring node alerted me to issues that all seem to funnel through HE. From my vantage point, the funnel is in Chicago and is still present: BlackBox-3:~ jlixfeld$ mtr -rwc 1 amazon08.ring.nlnog.net Start: Mon Jun 6 15:18:49 2016 HOST: BlackBox-3.local Loss% Snt Last Avg Best Wrst StDev 1.|-- vl4091.trs01.002.77mowatav01.yyz.beanfield.com 0.0% 1 2.7 2.7 2.7 2.7 0.0 2.|-- te0-2-0-2.bfr01.905kingstw01.yyz.beanfield.com 0.0% 1 2.3 2.3 2.3 2.3 0.0 3.|-- te-0-2-0-14.bfr01.151frontstw01.yyz.beanfield.com 0.0% 1 3.4 3.4 3.4 3.4 0.0 4.|-- he.ip4.torontointernetxchange.net 0.0% 1 2.2 2.2 2.2 2.2 0.0 5.|-- 100ge13-1.core1.chi1.he.net 0.0% 1 12.2 12.2 12.2 12.2 0.0 6.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 BlackBox-3:~ jlixfeld$
On Jun 6, 2016, at 3:15 PM, Josh Reynolds via Outages <outages@outages.org> wrote:
Just started seeing ipv4 issues here, glad somebody else popped up on the list.
Actually, it may have just resolved...
On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org> wrote:
Many IPv6 sites that I monitoring are repoting down ... the first few I checked are with HE:
root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed... root@nagios:~/tmp#
_______________________________________________ Outages mailing list Outages@outages.org https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiPs...
Outages mailing list Outages@outages.org https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiPs...
Two sites I was mtr'ing and go through HE in Chicago just cleared at 2:41 pm (U.S. Central), with traffic now flowing all the way through to the end site. Frank From: Jason Lixfeld [mailto:jason@lixfeld.ca] Sent: Monday, June 06, 2016 2:20 PM To: Josh Reynolds <josh@kyneticwifi.com> Cc: Frank Bulk <frnkblk@iname.com>; outages@outages.org Subject: Re: [outages] HE having an (IPv6) problem? My NLNOG ring node alerted me to issues that all seem to funnel through HE.
From my vantage point, the funnel is in Chicago and is still present:
BlackBox-3:~ jlixfeld$ mtr -rwc 1 amazon08.ring.nlnog.net Start: Mon Jun 6 15:18:49 2016 HOST: BlackBox-3.local Loss% Snt Last Avg Best Wrst StDev 1.|-- vl4091.trs01.002.77mowatav01.yyz.beanfield.com 0.0% 1 2.7 2.7 2.7 2.7 0.0 2.|-- te0-2-0-2.bfr01.905kingstw01.yyz.beanfield.com 0.0% 1 2.3 2.3 2.3 2.3 0.0 3.|-- te-0-2-0-14.bfr01.151frontstw01.yyz.beanfield.com 0.0% 1 3.4 3.4 3.4 3.4 0.0 4.|-- he.ip4.torontointernetxchange.net 0.0% 1 2.2 2.2 2.2 2.2 0.0 5.|-- 100ge13-1.core1.chi1.he.net 0.0% 1 12.2 12.2 12.2 12.2 0.0 6.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0 BlackBox-3:~ jlixfeld$ On Jun 6, 2016, at 3:15 PM, Josh Reynolds via Outages <outages@outages.org <mailto:outages@outages.org> > wrote: Just started seeing ipv4 issues here, glad somebody else popped up on the list. Actually, it may have just resolved. On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org <mailto:outages@outages.org> > wrote: Many IPv6 sites that I monitoring are repoting down . the first few I checked are with HE: root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com <http://www.informationweek.com> traceroute to www.informationweek.com <http://www.informationweek.com> (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed. root@nagios:~/tmp# _____________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiP snPIICjaezBRspaEkTna-2BGTD7ImngLs8On5UuzCoHdp1xCreK3JGf5CVNoQ-3D-3D_EYrXKctZ KQoD5HoQ3y4hTSX5fQxTW6SE1jlxL5-2FOOp1rqkgBOS4q4I8WRtMENLMQWhVUF-2BXXN3D9gKnV F7Wpnx9RXxiS3rftyhBczPDFISBpbJFAu8L7L-2B6ZJXFVAAIeNa5caKugTKgY222m0KnDsASjPX RkJA9LWbYHpFhRuK2icW9LGhbVpnmMkvakZ4fxZSwBYZ8lvOBX1q5Qvx-2FI3A-3D-3D> _____________________________________________ Outages mailing list Outages@outages.org <mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages <https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiP snPIICjaezBRspaEkTna-2BGTD7ImngLs8On5UuzCoHdp1xCreK3JGf5CVNoQ-3D-3D_EYrXKctZ KQoD5HoQ3y4hTSX5fQxTW6SE1jlxL5-2FOOp1rqkgBOS4q4I8WRtMENLMQj8zdb9JtGgXnNB-2Fi llghtZETk0L3t3pkQXcV7xOBz2BsDHZ3UAQXQCGwJ27-2FtydmsWF14EgsAz8MlgGWYES8RCtooi -2BfnDWVh-2F0ih1qnO8C6k9fWU4zHRYuIDjamVRsBZvXpS3kJ4RedHCGscJcgOA-3D-3D> <https://u3172041.ct.sendgrid.net/wf/open?upn=EYrXKctZKQoD5HoQ3y4hTSX5fQxTW6 SE1jlxL5-2FOOp1rqkgBOS4q4I8WRtMENLMQLK5M71pajXNIGEeI6yWO6Polz9xLq2xm-2FHaWnH FYFWjA7pXqf0FUrumZPmzGuBbtPZaehQvVPikqnqnhEBjpLoxH4DIWAanUJBcDisZm7QlI-2B7v5 fPtCe1yfhfxLaD-2BfOp7WHeLZqNJpRmBzHN1tug-3D-3D>
We've been having IPv4 peering issues since 14:30 CST. RTT to their peering routers has been all over the map - from 16ms up to 500ms. On 06/06/2016 02:19 PM, Jason Lixfeld via Outages wrote:
My NLNOG ring node alerted me to issues that all seem to funnel through HE. From my vantage point, the funnel is in Chicago and is still present:
BlackBox-3:~ jlixfeld$ mtr -rwc 1 amazon08.ring.nlnog.net Start: Mon Jun 6 15:18:49 2016 HOST: BlackBox-3.local Loss% Snt Last Avg Best Wrst StDev
1.|-- vl4091.trs01.002.77mowatav01.yyz.beanfield.com 0.0% 1 2.7 2.7 2.7 2.7 0.0 2.|-- te0-2-0-2.bfr01.905kingstw01.yyz.beanfield.com 0.0% 1 2.3 2.3 2.3 2.3 0.0 3.|-- te-0-2-0-14.bfr01.151frontstw01.yyz.beanfield.com 0.0% 1 3.4 3.4 3.4 3.4 0.0 4.|-- he.ip4.torontointernetxchange.net 0.0% 1 2.2 2.2 2.2 2.2 0.0 5.|-- 100ge13-1.core1.chi1.he.net 0.0% 1 12.2 12.2 12.2 12.2 0.0 6.|-- ??? 100.0 1 0.0 0.0 0.0 0.0 0.0
BlackBox-3:~ jlixfeld$
On Jun 6, 2016, at 3:15 PM, Josh Reynolds via Outages <outages@outages.org> wrote:
Just started seeing ipv4 issues here, glad somebody else popped up on the list.
Actually, it may have just resolved…
On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org> wrote:
Many IPv6 sites that I monitoring are repoting down … the first few I checked are with HE:
root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed… root@nagios:~/tmp#
/____________________________________________/_ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages <https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiPsnPIICjaezBRspaEkTna-2BGTD7ImngLs8On5UuzCoHdp1xCreK3JGf5CVNoQ-3D-3D_CFMke8FLYPmhaxdfTJT0okbcDuY-2BtBleGN-2FMczBM-2BZ96kFwoj2-2BGI4gtEmPKfK0r5RRi3TmD7IBvqJRRzOSXsx4rdGoGyFg-2BBPASTQa9T6y38ittQ1eJuYtXNmL1afcdRItUruoGl4zXW5WLGsCpqEkbz-2BP5qQ4ToLfVxdcPbsJ2N1-2FqhmcfMwaZ3mVXajEprXmubv7vgxxiXt6sx-2BhIzg-3D-3D>
/____________________________________________/_ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages <https://u3172041.ct.sendgrid.net/wf/click?upn=SDfLr6rsHpwHy-2BGX8pzvBx34QiPsnPIICjaezBRspaEkTna-2BGTD7ImngLs8On5UuzCoHdp1xCreK3JGf5CVNoQ-3D-3D_CFMke8FLYPmhaxdfTJT0okbcDuY-2BtBleGN-2FMczBM-2BZ96kFwoj2-2BGI4gtEmPKfK0rZQgOWNnXFVYnfhjPfjPrG1wRbgdINST8kmau9h0NHh3ygjBTYnaTwUfrB71euF3NUHbbGmi9qKl-2FNvf8s4RUa50RD4bNaGRLQ6widSsQzDdfn4Zpnl6WxGFFZ6-2FmV9WckldWxg0N-2Bv67oFkZ7eF-2BzA-3D-3D>
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- sjk@cupacoffee.net fingerprint: 1024D/89420B8E 2001-09-16 No one can understand the truth until he drinks of coffee's frothy goodness. ~Sheik Abd-al-Kadir
We contacted HE.net, they indicated they are aware of an issue int he Chicago market right now. No ETR however. *Nick Colton* Engineering Director ncolton@allophone.net office: 308.633.7814 610 Broadway, Imperial, NE 69033 allocommunications.com [image: ALLO | A Nelnet Company] <http://allocommunications.com/> Experience the Fiber Difference On Mon, Jun 6, 2016 at 1:15 PM, Josh Reynolds via Outages < outages@outages.org> wrote:
Just started seeing ipv4 issues here, glad somebody else popped up on the list.
Actually, it may have just resolved...
On Mon, Jun 6, 2016 at 2:10 PM, Frank Bulk via Outages <outages@outages.org> wrote:
Many IPv6 sites that I monitoring are repoting down ... the first few I checked are with HE:
root@nagios:~/tmp# tcptraceroute 6lab.cisco.com Selected device eth0.3, address 96.31.0.5, port 50468 for outgoing packets Tracing the path to 6lab.cisco.com (173.38.154.157) on TCP port 80 (www), 30 hops max 1 router-core-inside.mtcnet.net (96.31.0.254) 0.252 ms 0.266 ms 0.207 ms 2 sxct.spnc.mtcnet.net (167.142.156.194) 0.269 ms 0.180 ms 0.142 ms 3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.780 ms 4.752 ms 14.526 ms 4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.517 ms 8.685 ms 8.556 ms 5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.546 ms 8.579 ms 9.526 ms 6 v504.core1.oma1.he.net (184.105.18.169) 36.198 ms 30.499 ms 30.476 ms 7 *^C root@nagios:~/tmp# tcptraceroute6 www.informationweek.com traceroute to www.informationweek.com (2620:103::192:155:48:81) from 2607:fe28:0:1000::5, port 80, from port 43778, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.245 ms 0.211 ms 0.210 ms 2 sxct.spnc.mtcnet.net (2607:fe28:11:1002::194) 0.259 ms 0.148 ms 0.157 ms 3 v6-premier.movl-mlx.fbnt.netins.net (2001:5f8:7f0a:1::1) 5.014 ms 11.906 ms 4.972 ms 4 v6-ins-kb1-te-12-2-3031.kmrr.netins.net (2001:5f8:2:2::1) 8.780 ms 8.597 ms 8.589 ms 5 v6-ins-kc2-et-9-3.kmrr.netins.net (2001:5f8::27:1) 8.643 ms 8.605 ms 8.678 ms 6 10gigabitethernet9.switch1.oma1.he.net (2001:470:1:9a::1) 13.342 ms 16.310 ms 16.173 ms 7 10ge15-8.core1.den1.he.net (2001:470:0:332::1) 23.416 ms 23.457 ms 38.828 ms 8 asn-qwest-us-as209.10gigabitethernet13-2.core1.den1.he.net (2001:470:0:39f::2) 30.422 ms 30.385 ms 30.395 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * ^C46% completed... root@nagios:~/tmp#
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (5)
-
Frank Bulk -
Jason Lixfeld -
Josh Reynolds -
Nick Colton -
sjk