> On Sep 21, 2017, at 2:53 PM, Scott Larson <s...@wiredrive.com> wrote: > > I'm looking for a contact at Bell to look at a routing/traffic issue > we've been seeing since at least 5pm PDT yesterday. One of our uplinks is > via NTT and after correlating with their NOC, it appears traffic passing > through that link ends up dying inside the Bell network. >
% traceroute www.bell.ca traceroute to www.bell.ca (184.150.211.7), 30 hops max, 60 byte packets 1 Internal (x.x.x.x) 0.400 ms 0.436 ms 0.431 ms 2 ae-1.a01.chcgil09.us.bb.gin.ntt.net (129.250.5.94) 0.378 ms 0.412 ms 0.409 ms 3 ae-0.bell-canada.chcgil09.us.bb.gin.ntt.net (128.241.3.10) 0.765 ms bx4-chicagodt_pos0-1-0-1_core.net.bell.ca (64.230.186.217) 0.885 ms 0.979 ms 4 tcore3-chicagocp_0-10-0-0.net.bell.ca (64.230.79.84) 26.458 ms 26.501 ms tcore4-chicagocp_0-10-0-0.net.bell.ca (64.230.79.86) 23.043 ms 5 tcore4-toronto12_hundredgige1-2-0-0.net.bell.ca (64.230.79.156) 26.938 ms 26.939 ms 26.978 ms 6 tcore4-montreal01_hundredgige0-9-0-0.net.bell.ca (64.230.79.195) 26.487 ms tcore3-montreal02_1-7-0-0.net.bell.ca (64.230.79.31) 24.361 ms tcore4-montreal01_hundredgige0-9-0-0.net.bell.ca (64.230.79.195) 25.795 ms 7 tcore4-montreal02_pos0-7-0-0_core.net.bell.ca (64.230.168.98) 24.879 ms 24.859 ms tcore3-montrealak_pos0-13-0-0.net.bell.ca (64.230.32.117) 24.168 ms 8 agg2-montrealak_xe5-0-0.net.bell.ca (64.230.173.46) 25.591 ms 25.534 ms agg2-montrealak_xe7-0-0.net.bell.ca (64.230.173.38) 23.145 ms 9 dis1-montreal43_7-0-0.net.bell.ca (64.230.128.70) 23.254 ms 21.132 ms 33.596 ms 10 * * * 11 216.208.226.199 (216.208.226.199) 25.462 ms 25.444 ms 23.482 ms
