a bunch of us comcast soho folk, and monitoring gear, are seeing v4 breakage in orygon and maybe washington but only for seattle destinations. v6 works. johnb, is comcast going v6-only? :) ryuu.rg.net:/Users/randy> ping r0.iad PING r0.iad.rg.net (198.180.150.120): 56 data bytes 64 bytes from 198.180.150.120: icmp_seq=0 ttl=54 time=83.186 ms 64 bytes from 198.180.150.120: icmp_seq=1 ttl=54 time=81.450 ms ^C --- r0.iad.rg.net ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 81.450/82.318/83.186/0.868 ms ryuu.rg.net:/Users/randy> ping r0.sea PING r0.sea.rg.net (147.28.0.4): 56 data bytes Request timeout for icmp_seq 0 ^C --- r0.sea.rg.net ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss ryuu.rg.net:/Users/randy> ping6 r0.sea PING6(56=40+8+8 bytes) 2601:1c0:5600:9f4d:b500:3942:c8bd:ff16 --> 2001:418:1::4 16 bytes from 2001:418:1::4, icmp_seq=0 hlim=55 time=21.339 ms 16 bytes from 2001:418:1::4, icmp_seq=1 hlim=55 time=17.544 ms ^C --- r0.sea.rg.net ping6 statistics --- my guess is that it is up in seattle. but portland folk always blame seattle :) ryuu.rg.net:/Users/randy> traceroute r1.sea traceroute to r1.sea.rg.net (147.28.0.5), 64 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 5.382 ms 2.555 ms 1.978 ms 2 100.93.174.2 (100.93.174.2) 14.301 ms 100.93.174.3 (100.93.174.3) 16.307 ms 100.93.174.2 (100.93.174.2) 15.785 ms 3 po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 19.839 ms po-332-363-rur201.beaverton.or.bverton.comcast.net (96.108.64.181) 11.312 ms po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 17.453 ms 4 po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 14.082 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 13.606 ms po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 17.979 ms 5 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 20.961 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 15.522 ms * 6 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 12.324 ms * * 7 be-2312-pe12.seattle.wa.ibone.comcast.net (96.110.34.138) 20.785 ms be-36211-cs01.seattle.wa.ibone.comcast.net (68.86.93.49) 18.071 ms be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 15.331 ms 8 be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 26.953 ms * be-2412-pe12.seattle.wa.ibone.comcast.net (96.110.34.142) 19.355 ms 9 * * * 10 * * * ^C randy
John is no longer at the company - but Tony (cc'd) may be able to assist off-list. On 5/31/24, 14:58, "NANOG on behalf of Randy Bush" <nanog-bounces+jason_livingood=cable.comcast.com@nanog.org <mailto:cable.comcast.com@nanog.org> on behalf of randy@psg.com <mailto:randy@psg.com>> wrote: a bunch of us comcast soho folk, and monitoring gear, are seeing v4 breakage in orygon and maybe washington but only for seattle destinations. v6 works. johnb, is comcast going v6-only? :) ryuu.rg.net:/Users/randy> ping r0.iad PING r0.iad.rg.net (198.180.150.120): 56 data bytes 64 bytes from 198.180.150.120: icmp_seq=0 ttl=54 time=83.186 ms 64 bytes from 198.180.150.120: icmp_seq=1 ttl=54 time=81.450 ms ^C --- r0.iad.rg.net ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 81.450/82.318/83.186/0.868 ms ryuu.rg.net:/Users/randy> ping r0.sea PING r0.sea.rg.net (147.28.0.4): 56 data bytes Request timeout for icmp_seq 0 ^C --- r0.sea.rg.net ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss ryuu.rg.net:/Users/randy> ping6 r0.sea PING6(56=40+8+8 bytes) 2601:1c0:5600:9f4d:b500:3942:c8bd:ff16 --> 2001:418:1::4 16 bytes from 2001:418:1::4, icmp_seq=0 hlim=55 time=21.339 ms 16 bytes from 2001:418:1::4, icmp_seq=1 hlim=55 time=17.544 ms ^C --- r0.sea.rg.net ping6 statistics --- my guess is that it is up in seattle. but portland folk always blame seattle :) ryuu.rg.net:/Users/randy> traceroute r1.sea traceroute to r1.sea.rg.net (147.28.0.5), 64 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 5.382 ms 2.555 ms 1.978 ms 2 100.93.174.2 (100.93.174.2) 14.301 ms 100.93.174.3 (100.93.174.3) 16.307 ms 100.93.174.2 (100.93.174.2) 15.785 ms 3 po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 19.839 ms po-332-363-rur201.beaverton.or.bverton.comcast.net (96.108.64.181) 11.312 ms po-332-364-rur202.beaverton.or.bverton.comcast.net (96.108.64.189) 17.453 ms 4 po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 14.082 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 13.606 ms po-2-rur202.beaverton.or.bverton.comcast.net (24.124.129.106) 17.979 ms 5 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 20.961 ms po-200-xar02.beaverton.or.bverton.comcast.net (96.216.60.165) 15.522 ms * 6 ae-69-ar01.troutdale.or.bverton.comcast.net (68.85.243.197) 12.324 ms * * 7 be-2312-pe12.seattle.wa.ibone.comcast.net (96.110.34.138) 20.785 ms be-36211-cs01.seattle.wa.ibone.comcast.net (68.86.93.49) 18.071 ms be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 15.331 ms 8 be-2212-pe12.seattle.wa.ibone.comcast.net (96.110.34.134) 26.953 ms * be-2412-pe12.seattle.wa.ibone.comcast.net (96.110.34.142) 19.355 ms 9 * * * 10 * * * ^C randy
kinda summary: comcast and cogent/sprint very helpful. likely cause a misconfig in cogent norcal when trying to route around a power outage in seattle. fwiw, HE and IIJ IPv6 transit (tyvm) in seattle allowed us to keep working through the outage. randy
participants (2)
-
Livingood, Jason -
Randy Bush