
I'm unable to ping or resolve DNS via 1.1.1.1 from a residential Spectrum/TWC link this morning. Some traceroutes: traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 38 byte packets
1 * * * 2 be53.nycynymy02h.nyc.rr.com (68.173.202.106) 16.117 ms 11.746 ms 10.082 ms 3 agg113.nyquny9101r.nyc.rr.com (68.173.198.42) 11.597 ms 17.395 ms 15.993 ms 4 bu-ether15.nycmny837aw-bcr00.tbone.rr.com (66.109.6.76) 21.174 ms bu-ether25.nycmny837aw-bcr00.tbone.rr.com (107.14.19.22) 19.003 ms 17.775 ms 5 0.ae1.pr0.nyc20.tbone.rr.com (66.109.6.163) 13.580 ms 12.822 ms 11.535 ms 6 ix-ae-6-0.tcore1.n75-new-york.as6453.net (66.110.96.53) 11.519 ms ix-ae-10-0.tcore1.n75-new-york.as6453.net (66.110.96.13) 14.487 ms ix-ae-6-0.tcore1.n75-new-york.as6453.net (66.110.96.53) 10.286 ms 7 if-ae-9-2.tcore1.nto-new-york.as6453.net (63.243.128.121) 14.701 ms 10.585 ms 13.350 ms 8 if-ae-7-2.tcore1.n0v-new-york.as6453.net (63.243.128.26) 11.680 ms 14.768 ms 13.893 ms 9 if-ae-0-2.tcore3.njy-newark.as6453.net (216.6.90.14) 14.285 ms 12.967 ms 11.413 ms 10 * * * # continues
1.0.0.1 is OK: traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 38 byte packets 1 * * * 2 be53.nycynymy02h.nyc.rr.com (68.173.202.106) 13.131 ms 15.640 ms
11.649 ms
3 agg113.nyquny9101r.nyc.rr.com (68.173.198.42) 14.963 ms 11.888 ms
15.307 ms
4 bu-ether25.nycmny837aw-bcr00.tbone.rr.com (107.14.19.22) 12.224 ms
16.483 ms 12.216 ms
5 0.ae4.pr0.nyc20.tbone.rr.com (66.109.1.35) 12.927 ms
0.ae0.pr0.nyc20.tbone.rr.com (66.109.6.157) 39.476 ms 0.ae2.pr0.nyc20.tbone.rr.com (107.14.19.147) 18.148 ms
6 ix-ae-10-0.tcore1.n75-new-york.as6453.net (66.110.96.13) 13.181 ms
11.928 ms ix-ae-6-0.tcore1.n75-new-york.as6453.net (66.110.96.53) 11.376 ms
7 if-ae-9-2.tcore1.nto-new-york.as6453.net (63.243.128.121) 18.645 ms
11.686 ms 14.363 ms
8 if-ae-7-2.tcore1.n0v-new-york.as6453.net (63.243.128.26) 13.445 ms
11.262 ms 18.950 ms
9 if-ae-0-2.tcore3.njy-newark.as6453.net (216.6.90.14) 12.794 ms 13.087
ms 15.162 ms
10 if-ae-1-3.tcore4.njy-newark.as6453.net (216.6.57.6) 13.003 ms 13.582
ms 14.550 ms
11 66.198.70.2 (66.198.70.2) 16.251 ms 16.419 ms 10.120 ms 12 one.one.one.one (1.0.0.1) 13.237 ms 11.032 ms 9.490 ms Using Tata's AS6453 looking glass ( http://lg.as6453.net/lg/ ) from any NY router seems to confirm trouble there: Router: gin-njy-tcore3
Site: US, Newark, NJY Command: ping inet count 5 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes --- 1.1.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss

On Mon, Jan 28, 2019 at 08:42:01AM -0500, Nick Lopez via Outages wrote:
Using Tata's AS6453 looking glass ( http://lg.as6453.net/lg/ ) from any NY router seems to confirm trouble there:
Router: gin-njy-tcore3
Site: US, Newark, NJY Command: ping inet count 5 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes --- 1.1.1.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss
Looks like it's fixed. http://lg.as6453.net/lg/ AS6453 IPv4 and IPv6 Looking Glass traceroute inet4 1.1.1.1 as-number-lookup Router: gin-njy-tcore3 Site: US, Newark, NJY Command: traceroute inet4 1.1.1.1 as-number-lookup traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 52 byte packets 1 if-ae-1-3.tcore4.njy-newark.as6453.net (216.6.57.6) 8.800 ms 6.155 ms 6.023 ms MPLS Label=339544 CoS=0 TTL=1 S=1 2 if-ae-12-2.tcore2.aeq-ashburn.as6453.net (216.6.87.42) 5.895 ms if-ae-12-4.tcore2.aeq-ashburn.as6453.net (216.6.87.222) 5.918 ms 5.942 ms 3 216.6.87.221 (216.6.87.221) 7.148 ms 7.060 ms 6.402 ms 4 one.one.one.one (1.1.1.1) [AS 13335] 5.613 ms 7.168 ms 5.706 ms Regards, -- Nicolas Hyvernat
participants (2)
-
Nick Lopez
-
Nicolas Hyvernat