We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on? Specifically we're trying to get to 132.60.10.110: PS H:\> tracert ausis.maxwell.af.mil Tracing route to ausis.maxwell.af.mil [132.60.10.110] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1] 2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97] 3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9] 4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77] 5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37] 6 11 ms 11 ms 10 ms 12.250.16.17 7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138] 8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157] 9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217] 10 * * * Request timed out. 11 33 ms 33 ms 33 ms 67.133.228.2 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 <%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/
I die at the same router, coming in from Level3 Jim Limmer, CISSP < Information Security Officer Systems and Network Architect > From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org Subject: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16 We're having problems getting to anything in the 132.60.0.0/16<http://132.60.0.0/16> net block from 141.219.0.0/16<http://141.219.0.0/16>. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on? Specifically we're trying to get to 132.60.10.110<http://132.60.10.110>: PS H:\> tracert ausis.maxwell.af.mil<http://ausis.maxwell.af.mil> Tracing route to ausis.maxwell.af.mil<http://ausis.maxwell.af.mil> [132.60.10.110] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu<http://mx480-07-001-staff-it-z16.tc.mtu.edu> [141.219.40.1] 2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu<http://mx80-07-002.tc.mtu.edu> [141.219.183.97] 3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net<http://xe-0-0-3.hgtn-cor-mtu.mich.net> [207.75.40.9] 4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net<http://irbx70.pwrs-cor-powers.mich.net> [198.108.22.77] 5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net<http://ae1x18.eq-chi2.mich.net> [198.108.22.37] 6 11 ms 11 ms 10 ms 12.250.16.17 7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net<http://cr2.cgcil.ip.att.net> [12.122.132.138] 8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net<http://cgr1.cgcil.ip.att.net> [12.122.132.157] 9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net<http://chp-brdr-03.inet.qwest.net> [63.146.26.217] 10 * * * Request timed out. 11 33 ms 33 ms 33 ms 67.133.228.2 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696<tel:%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org
wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Matt Freitag via Outages *Sent:* Wednesday, June 08, 2016 10:39 AM *To:* outages@outages.org *Subject:* [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Looks like the peering point Qwest is handing off to is the culprit Sent from my iPhone On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org<mailto:outages@outages.org>> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org<mailto:outages@outages.org>> wrote: I die at the same router, coming in from Level3 Jim Limmer, CISSP < Information Security Officer Systems and Network Architect > From: Outages [mailto:outages-bounces@outages.org<mailto:outages-bounces@outages.org>] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org<mailto:outages@outages.org> Subject: [outages] Cannot access 132.60.0.0/16<http://132.60.0.0/16> from 141.219.0.0/16<http://141.219.0.0/16> We're having problems getting to anything in the 132.60.0.0/16<http://132.60.0.0/16> net block from 141.219.0.0/16<http://141.219.0.0/16>. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on? Specifically we're trying to get to 132.60.10.110<http://132.60.10.110>: PS H:\> tracert ausis.maxwell.af.mil<http://ausis.maxwell.af.mil> Tracing route to ausis.maxwell.af.mil<http://ausis.maxwell.af.mil> [132.60.10.110] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu<http://mx480-07-001-staff-it-z16.tc.mtu.edu> [141.219.40.1] 2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu<http://mx80-07-002.tc.mtu.edu> [141.219.183.97] 3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net<http://xe-0-0-3.hgtn-cor-mtu.mich.net> [207.75.40.9] 4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net<http://irbx70.pwrs-cor-powers.mich.net> [198.108.22.77] 5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net<http://ae1x18.eq-chi2.mich.net> [198.108.22.37] 6 11 ms 11 ms 10 ms 12.250.16.17 7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net<http://cr2.cgcil.ip.att.net> [12.122.132.138] 8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net<http://cgr1.cgcil.ip.att.net> [12.122.132.157] 9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net<http://chp-brdr-03.inet.qwest.net> [63.146.26.217] 10 * * * Request timed out. 11 33 ms 33 ms 33 ms 67.133.228.2 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696<tel:%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/ _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org<mailto:Outages@outages.org> https://puck.nether.net/mailman/listinfo/outages
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4 Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 <%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/ On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages < outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages < outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Matt Freitag via Outages *Sent:* Wednesday, June 08, 2016 10:39 AM *To:* outages@outages.org *Subject:* [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Actually, I can't seem to get to any of the prefixes at the US Department of Defense... Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 <%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/ On Wed, Jun 8, 2016 at 10:54 AM, Matt Freitag <mlfreita@mtu.edu> wrote:
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 <%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages < outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages < outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages < outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Matt Freitag via Outages *Sent:* Wednesday, June 08, 2016 10:39 AM *To:* outages@outages.org *Subject:* [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* the target IP (18th & 19th hop) and keeps on going.... $ traceroute 132.60.10.110 traceroute to 132.60.10.110 (132.60.10.110), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 4.847 ms 0.775 ms 0.729 ms 2 10.7.120.1 (10.7.120.1) 24.318 ms 23.881 ms 23.799 ms 3 g0-5-3-2.phlapa-lcr-21.verizon-gni.net (130.81.193.156) 25.839 ms 27.322 ms 28.054 ms 4 * * * 5 * * * 6 140.222.230.249 (140.222.230.249) 28.971 ms 30.500 ms 29.107 ms 7 63-235-40-49.dia.static.qwest.net (63.235.40.49) 29.777 ms 30.166 ms 30.333 ms 8 frp-edge-06.inet.qwest.net (67.14.31.222) 64.505 ms 65.422 ms 64.512 ms 9 67.133.228.2 (67.133.228.2) 66.473 ms 66.183 ms 65.948 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 100.50.1.1 (100.50.1.1) 68.667 ms 68.542 ms 68.992 ms 16 * * * 17 * * * 18 132.60.10.110 (132.60.10.110) 66.489 ms 66.270 ms 66.555 ms 19 132.60.10.110 (132.60.10.110) 67.895 ms 68.194 ms 68.009 ms 20 * * * 21 * * * 22 140.14.52.33 (140.14.52.33) 88.105 ms 67.567 ms 67.976 ms 23 * * * 24 * * * 25 214.40.23.10 (214.40.23.10) 85.446 ms 84.989 ms 85.437 ms 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * 31 * * * On Wed, Jun 8, 2016 at 10:57 AM, Matt Freitag via Outages <outages@outages.org> wrote:
Actually, I can't seem to get to any of the prefixes at the US Department of Defense...
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:54 AM, Matt Freitag <mlfreita@mtu.edu> wrote:
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages <outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org Subject: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ 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
That's definitely different. And earlier when I said "I can't get at any prefix announced by the DoD" what I meant was I can't get at anything announced by/through AS721, the DoD Network Information Center. Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 <%28906%29%20487-3696> https://www.mtu.edu/ https://www.it.mtu.edu/ On Wed, Jun 8, 2016 at 11:38 AM, Jay Farrell via Outages < outages@outages.org> wrote:
Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* the target IP (18th & 19th hop) and keeps on going....
$ traceroute 132.60.10.110
traceroute to 132.60.10.110 (132.60.10.110), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.847 ms 0.775 ms 0.729 ms
2 10.7.120.1 (10.7.120.1) 24.318 ms 23.881 ms 23.799 ms
3 g0-5-3-2.phlapa-lcr-21.verizon-gni.net (130.81.193.156) 25.839 ms 27.322 ms 28.054 ms
4 * * *
5 * * *
6 140.222.230.249 (140.222.230.249) 28.971 ms 30.500 ms 29.107 ms
7 63-235-40-49.dia.static.qwest.net (63.235.40.49) 29.777 ms 30.166 ms 30.333 ms
8 frp-edge-06.inet.qwest.net (67.14.31.222) 64.505 ms 65.422 ms 64.512 ms
9 67.133.228.2 (67.133.228.2) 66.473 ms 66.183 ms 65.948 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 100.50.1.1 (100.50.1.1) 68.667 ms 68.542 ms 68.992 ms
16 * * *
17 * * *
18 132.60.10.110 (132.60.10.110) 66.489 ms 66.270 ms 66.555 ms
19 132.60.10.110 (132.60.10.110) 67.895 ms 68.194 ms 68.009 ms
20 * * *
21 * * *
22 140.14.52.33 (140.14.52.33) 88.105 ms 67.567 ms 67.976 ms
23 * * *
24 * * *
25 214.40.23.10 (214.40.23.10) 85.446 ms 84.989 ms 85.437 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
On Wed, Jun 8, 2016 at 10:57 AM, Matt Freitag via Outages <outages@outages.org> wrote:
Actually, I can't seem to get to any of the prefixes at the US Department of Defense...
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:54 AM, Matt Freitag <mlfreita@mtu.edu> wrote:
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages <outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org Subject: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net
block
from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157 ]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
My trace looked just like this. It's as if some probes reach the destination, but other probes spin off into Neverland. On Wed, Jun 8, 2016 at 9:38 AM, Jay Farrell via Outages <outages@outages.org
wrote:
Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* the target IP (18th & 19th hop) and keeps on going....
$ traceroute 132.60.10.110
traceroute to 132.60.10.110 (132.60.10.110), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.847 ms 0.775 ms 0.729 ms
2 10.7.120.1 (10.7.120.1) 24.318 ms 23.881 ms 23.799 ms
3 g0-5-3-2.phlapa-lcr-21.verizon-gni.net (130.81.193.156) 25.839 ms 27.322 ms 28.054 ms
4 * * *
5 * * *
6 140.222.230.249 (140.222.230.249) 28.971 ms 30.500 ms 29.107 ms
7 63-235-40-49.dia.static.qwest.net (63.235.40.49) 29.777 ms 30.166 ms 30.333 ms
8 frp-edge-06.inet.qwest.net (67.14.31.222) 64.505 ms 65.422 ms 64.512 ms
9 67.133.228.2 (67.133.228.2) 66.473 ms 66.183 ms 65.948 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 100.50.1.1 (100.50.1.1) 68.667 ms 68.542 ms 68.992 ms
16 * * *
17 * * *
18 132.60.10.110 (132.60.10.110) 66.489 ms 66.270 ms 66.555 ms
19 132.60.10.110 (132.60.10.110) 67.895 ms 68.194 ms 68.009 ms
20 * * *
21 * * *
22 140.14.52.33 (140.14.52.33) 88.105 ms 67.567 ms 67.976 ms
23 * * *
24 * * *
25 214.40.23.10 (214.40.23.10) 85.446 ms 84.989 ms 85.437 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
On Wed, Jun 8, 2016 at 10:57 AM, Matt Freitag via Outages <outages@outages.org> wrote:
Actually, I can't seem to get to any of the prefixes at the US Department of Defense...
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:54 AM, Matt Freitag <mlfreita@mtu.edu> wrote:
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages <outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org Subject: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net
block
from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157 ]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Those 2 later neverland hops are also DoD IPs, fwiw. On Wed, Jun 8, 2016 at 11:44 AM, John Neiberger <jneiberger@gmail.com> wrote:
My trace looked just like this. It's as if some probes reach the destination, but other probes spin off into Neverland.
On Wed, Jun 8, 2016 at 9:38 AM, Jay Farrell via Outages <outages@outages.org> wrote:
Here's an odd trace from Verizon DSL in phl; traceroute *passes thru* the target IP (18th & 19th hop) and keeps on going....
$ traceroute 132.60.10.110
traceroute to 132.60.10.110 (132.60.10.110), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.847 ms 0.775 ms 0.729 ms
2 10.7.120.1 (10.7.120.1) 24.318 ms 23.881 ms 23.799 ms
3 g0-5-3-2.phlapa-lcr-21.verizon-gni.net (130.81.193.156) 25.839 ms 27.322 ms 28.054 ms
4 * * *
5 * * *
6 140.222.230.249 (140.222.230.249) 28.971 ms 30.500 ms 29.107 ms
7 63-235-40-49.dia.static.qwest.net (63.235.40.49) 29.777 ms 30.166 ms 30.333 ms
8 frp-edge-06.inet.qwest.net (67.14.31.222) 64.505 ms 65.422 ms 64.512 ms
9 67.133.228.2 (67.133.228.2) 66.473 ms 66.183 ms 65.948 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 100.50.1.1 (100.50.1.1) 68.667 ms 68.542 ms 68.992 ms
16 * * *
17 * * *
18 132.60.10.110 (132.60.10.110) 66.489 ms 66.270 ms 66.555 ms
19 132.60.10.110 (132.60.10.110) 67.895 ms 68.194 ms 68.009 ms
20 * * *
21 * * *
22 140.14.52.33 (140.14.52.33) 88.105 ms 67.567 ms 67.976 ms
23 * * *
24 * * *
25 214.40.23.10 (214.40.23.10) 85.446 ms 84.989 ms 85.437 ms
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
On Wed, Jun 8, 2016 at 10:57 AM, Matt Freitag via Outages <outages@outages.org> wrote:
Actually, I can't seem to get to any of the prefixes at the US Department of Defense...
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:54 AM, Matt Freitag <mlfreita@mtu.edu> wrote:
Looks like that's the DoD Network Information Center: http://bgp.he.net/AS395#_graph4
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
On Wed, Jun 8, 2016 at 10:53 AM, David Palmerton via Outages <outages@outages.org> wrote:
Looks like the peering point Qwest is handing off to is the culprit
Sent from my iPhone
On Jun 8, 2016, at 10:51 AM, Dovid Bender via Outages <outages@outages.org> wrote:
From HE and NTT it dies on quests network. The last responding hop is 67.133.228.2
On Wed, Jun 8, 2016 at 10:43 AM, Jim Limmer via Outages <outages@outages.org> wrote:
I die at the same router, coming in from Level3
Jim Limmer, CISSP
< Information Security Officer
Systems and Network Architect >
From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Matt Freitag via Outages Sent: Wednesday, June 08, 2016 10:39 AM To: outages@outages.org Subject: [outages] Cannot access 132.60.0.0/16 from 141.219.0.0/16
We're having problems getting to anything in the 132.60.0.0/16 net block from 141.219.0.0/16. A traceroute shows traffic gets lost somewhere in Qwest's network. Trace is below. Is anyone else having this issue? Is someone from Qwest listening who has insight into what's going on?
Specifically we're trying to get to 132.60.10.110:
PS H:\> tracert ausis.maxwell.af.mil
Tracing route to ausis.maxwell.af.mil [132.60.10.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms mx480-07-001-staff-it-z16.tc.mtu.edu [141.219.40.1]
2 <1 ms <1 ms <1 ms mx80-07-002.tc.mtu.edu [141.219.183.97]
3 1 ms 1 ms <1 ms xe-0-0-3.hgtn-cor-mtu.mich.net [207.75.40.9]
4 4 ms 4 ms 4 ms irbx70.pwrs-cor-powers.mich.net [198.108.22.77]
5 10 ms 10 ms 10 ms ae1x18.eq-chi2.mich.net [198.108.22.37]
6 11 ms 11 ms 10 ms 12.250.16.17
7 14 ms 11 ms 11 ms cr2.cgcil.ip.att.net [12.122.132.138]
8 14 ms 11 ms 15 ms cgr1.cgcil.ip.att.net [12.122.132.157]
9 11 ms 11 ms 11 ms chp-brdr-03.inet.qwest.net [63.146.26.217]
10 * * * Request timed out.
11 33 ms 33 ms 33 ms 67.133.228.2
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Matt Freitag Network Engineer I Information Technology Michigan Technological University (906) 487-3696 https://www.mtu.edu/ https://www.it.mtu.edu/
_______________________________________________ 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
_______________________________________________ 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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
this is what i'm seeing from the us west coast. #sho ip bgp 132.60.10.110/32 shorter-prefixes Network Next Hop Metric LocPrf Weight Path * 132.0.0.0/10 38.122.146.105 3031 100 174 209 721 i *> 12.122.125.166 100 7018 209 721 i * 132.60.0.0 38.122.146.105 3031 100 174 209 721 27064 395 i *> 12.122.125.166 100 7018 209 721 27064 395 i #traceroute 132.60.10.110 Type escape sequence to abort. Tracing the route to 132.60.10.110 VRF info: (vrf in name/id, vrf out name/id) 1 12.116.189.221 [AS 7018] 1 msec 1 msec 2 msec 2 12.122.109.114 [AS 7018] [MPLS: Label 16994 Exp 1] 7 msec 7 msec 8 msec 3 * * * 4 12.122.129.97 [AS 7018] 9 msec 6 msec 8 msec 5 63.146.27.101 [AS 209] 4 msec 5 msec 4 msec 6 * * * 7 67.133.228.2 [AS 209] 57 msec 54 msec 54 msec 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 100.50.1.1 [AS 10507] 55 msec 54 msec 55 msec 14 * * * 15 * * * 16 132.60.10.110 [AS 395] 55 msec 55 msec 55 msec 17 132.60.10.110 [AS 395] 56 msec 56 msec 57 msec 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 214.40.23.10 [AS 27064] 73 msec 72 msec 73 msec 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * james
participants (7)
-
David Palmerton -
Dovid Bender -
james machado -
Jay Farrell -
Jim Limmer -
John Neiberger -
Matt Freitag