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/
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
