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 <m...@matthewmcclatchey.com> 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?
