Matt, I would recommend you look at RIPE Atlas for an answer. However, I did the following (start date being 8/21, end date being 8/23, asn being 2856):
curl -sS " https://atlas.ripe.net:443/api/v2/probes/?asn=2856&status=1&is_public=true"; > as2556-probes.json start=`date -u -j 08210000 +%s` ; stop=`date -u -j 08230000 +%s` probe_ids=`jq -r '.results[]|.id' < as2556-probes.json | tr '\012' ',' | sed -e 's/,$//'` curl -sS " https://atlas.ripe.net:443/api/v2/measurements/1001/results?start=$start&stop=$stop&probe_ids=$probe_ids&format=json"; > k-root-meeasurements.json jq -r '.[]|.prb_id,.timestamp,.result[0].rtt,.result[1].rtt,.result[2].rtt' < k-root-meeasurements.json | paste - - - - - | sort -n > results.tsv There are 51 working RIPE Atlas probes in BT's AS2856. That seemed like a good number. This set of commands produced the ping results for k-root (run by RIPE); which is part of the base measurements on all Atlas probes. This (I thought) would help show that your issue was indeed a BT to RIPE issue. egrep null < results.tsv | sort -bnk2,3 | while read prb_id ctime rtt1 rtt2 rtt3 ; do echo $prb_id `date -u -r $ctime +'%A %H:%M:%S'` $rtt1 $rtt2 $rtt3 ; done | column -t 6843 Friday 03:42:56 null 12.066932 11.927066 6843 Friday 09:02:53 12.852935 12.360774 null 6843 Friday 11:38:56 null 12.41469 null 22519 Friday 13:06:50 29.588305 12.19933 null 11983 Friday 13:38:15 316.167285 1187.264855 null 11983 Friday 14:06:15 11.6507 8.17299 null 11983 Friday 14:10:16 null 1375.160355 null 22028 Friday 21:42:31 220.65586 67.804055 null 33208 Friday 22:54:39 39.886735 39.64385 null 10139 Saturday 00:27:36 null null null 6843 Saturday 01:30:54 12.605508 13.131636 null 6843 Saturday 03:34:56 null 13.18357 13.015613 22519 Saturday 15:50:49 null 70.46346 72.902635 14370 Saturday 17:16:23 null null null 54495 Saturday 18:11:30 26.585333 26.595625 null 28349 Saturday 18:50:49 8.127585 9.13024 null 14285 Saturday 19:20:40 null null null 28349 Saturday 19:42:47 8.21941 7.93423 null 22028 Saturday 20:06:30 66.08535 151.76015 null 22028 Saturday 20:50:28 227.37915 623.43919 null 22028 Saturday 20:58:31 57.966505 146.43325 null 22028 Saturday 21:42:30 null 1018.01835 649.08021 22519 Saturday 22:38:47 12.635435 12.539535 null 17527 Saturday 22:53:15 null 18.31303 14.206965 I also plotted the results - yet I saw nothing out of the norm. You can do the same with the script above. The data is there and it's public. Enjoy, Martin On Sat, Aug 22, 2020 at 8:41 AM Matt McClatchey <[email protected]> wrote: > Hi all, > > 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? > > Matt >
