Thanks Paul. I’m still seeing issues here from three different BT Infinity FTTC connections. I can reach as far as *.nl-ams2.gia.bt.net, and then start to hit timeouts. Virgin Media in the same area works fine.
$ traceroute -I ripe.net traceroute to ripe.net (193.0.6.139), 30 hops max, 60 byte packets 1 _gateway (10.2.0.1) 1.143 ms 1.684 ms 2.571 ms 2 172.16.19.39 (172.16.19.39) 5.510 ms 5.507 ms 5.551 ms 3 * * * 4 31.55.186.220 (31.55.186.220) 21.932 ms 21.930 ms 21.927 ms 5 213.121.192.144 (213.121.192.144) 21.391 ms 21.670 ms 21.896 ms 6 166-49-209-132.gia.bt.net (166.49.209.132) 18.559 ms 18.880 ms 18.709 ms 7 t2c3-et-7-3-0.nl-ams2.gia.bt.net (166.49.195.174) 24.184 ms 23.904 ms 24.102 ms 8 * * * 9 * * * …. 30 * * * $ traceroute -I atlas.ripe.net traceroute to atlas.ripe.net (193.0.6.158), 30 hops max, 60 byte packets 1 _gateway (10.2.0.1) 1.063 ms 1.292 ms 1.562 ms 2 172.16.19.39 (172.16.19.39) 4.963 ms 5.185 ms 5.359 ms 3 * * * 4 31.55.186.208 (31.55.186.208) 19.533 ms 19.785 ms 20.410 ms 5 host213-121-192-48.ukcore.bt.net (213.121.192.48) 17.413 ms 17.622 ms 18.322 ms 6 166-49-209-132.gia.bt.net (166.49.209.132) 42.807 ms 43.140 ms 43.325 ms 7 t2c3-et-7-1-0.nl-ams2.gia.bt.net (166.49.195.170) 21.316 ms 22.121 ms 22.944 ms 8 * * * 9 * * * …. 30 * * * Interestingly, I just checked my probe on the Atlas website through a different ISP and apparently it’s connected. Looks like it’s able to reach ctr-ams02.atlas.ripe.net, so some of the Atlas services are accessible but not whois or the RIPE NCC websites. $ traceroute -I ctr-ams02.atlas.ripe.net traceroute to ctr-ams02.atlas.ripe.net (193.0.19.59), 30 hops max, 60 byte packets 1 _gateway (10.2.0.1) 1.904 ms 2.087 ms 2.320 ms 2 172.16.19.39 (172.16.19.39) 6.125 ms 6.417 ms 6.617 ms 3 31.55.186.193 (31.55.186.193) 21.263 ms 21.387 ms 21.641 ms 4 31.55.186.208 (31.55.186.208) 19.638 ms 19.789 ms 19.931 ms 5 195.99.127.88 (195.99.127.88) 21.784 ms 21.775 ms 21.939 ms 6 166-49-209-132.gia.bt.net (166.49.209.132) 27.935 ms 25.899 ms 26.078 ms 7 t2c3-et-7-3-0.nl-ams2.gia.bt.net (166.49.195.174) 24.610 ms 23.889 ms 24.422 ms 8 * * * 9 * * * 10 ctr-ams02.atlas.ripe.net (193.0.19.59) 23.251 ms 23.468 ms 23.720 ms $ whois --verbose 193.0.19.59 Using server whois.ripe.net. Query string: "-V Md5.5.6 193.0.19.59" connect: Network is unreachable Matt On Sat, Aug 22, 2020 at 9:04 PM Paul Mansfield <[email protected]> wrote: > it's working for me (TM). From Zen FTTC. > > My probe says it's only been connected for just under 13 hours, and > it's 21:00 (BST) now so that means RIPE think it connected at 08:00 > ish. > https://atlas.ripe.net/probes/12349/#tab-general > > I know that my connection has been up since 2020-08-21 03:36 BST, so I > can't explain why RIPE think my probe hasn't been online for longer. I > didn't get any emails about it being offline. > > Just in case it helps, here's a traceroute: > # traceroute -I atlas.ripe.net > traceroute to atlas.ripe.net (193.0.6.158), 30 hops max, 60 byte packets > 1 losubs.subs.bng1.th-lon.zen.net.uk (62.3.80.17) 7.688 ms 7.626 > ms 7.602 ms > 2 ae1-177.cr2.th-lon.zen.net.uk (62.3.80.38) 7.578 ms 7.559 ms 7.540 > ms > 3 vl-50.ae-5.pe2.thn-lon.zen.net.uk (51.148.73.54) 7.956 ms 7.947 > ms 7.938 ms > 4 ae-1.br2.thn-lon.zen.net.uk (51.148.73.119) 8.522 ms 8.514 ms > 8.507 ms > 5 195.66.225.24 (195.66.225.24) 8.491 ms 8.483 ms 8.588 ms > 6 something.surf.net (109.105.98.110) 13.870 ms 12.560 ms 12.494 ms > 7 gw.amsix.eqix3rtr.ripe.net (80.249.208.68) 12.713 ms !X 12.643 > ms !X 12.590 ms !X > > > On Sat, 22 Aug 2020 at 16:41, Matt McClatchey > <[email protected]> wrote: > > I've been unable to access RIPE NCC services from multiple BT broadband > connections from AS2856 in Belfast today. This includes ripe.net, > whois.ripe.net, atlas.ripe.net, stat.ripe.net, which all appear to be up > from other networks. My Atlas probe apparently disconnected at about 06:45 > this morning - I assume that's around when the issue started. > > > > Has anyone else been experiencing this, or have any insight? >
