Hi Michiel,

On 2023-03-24 16:55:27, you wrote to Nigel Reed:

 NR>>> According to their website, it's already closed.

 MV>> 1:134/101 wirh IPv6 address 2a06:a004:4020:beef:f1d0:1:134:101 is
 MV>> still online...

 MvdV> Not any more...

 MvdV> Same for 1:134/0, 100, 102, 103, 301, 302, 303

 MvdV> Ergo: the entire net 134 is down except for 1:134/303 that still answers on
 MvdV> IPv4.

I can confirm that:

1:134/0 nc.fido134.net:24554    2a06:a004:4020:beef:f1d0:1:134:0        Error: Connection timed out
1:134/0 nc.fido134.net:24554    198.48.156.169  Error: Connection timed out
1:134/100       echohub.fido134.net:24554       2a06:a004:4020:beef:f1d0:1:134:100      Error: Connection timed out
1:134/100       echohub.fido134.net:24554       178.128.187.153 Error: Socket read error.
1:134/101       binkp.undermine.ca:24554        2a06:a004:4020:beef:f1d0:1:134:101      Error: Connection timed out
1:134/101       binkp.undermine.ca:24554        198.48.156.169  Error: Connection timed out
1:134/102       shellshockbbs.ddns.net:24554    2600:70ff:b88a:ab:f1d0:1:134:102        Error: Connection timed out
1:134/103       bbs.technocentrist.com:24554    172.105.22.6    Error: Connection refused
1:134/301       i2ibbs.ddns.net:24569   2600:70ff:b88a:ab:f1d0:1:134:301        Error: Connection timed out
1:134/302       bbs.epochbbs.com:24554  2a06:a004:4020:beef:f1d0:1:134:302      Error: Connection timed out
1:134/302       bbs.epochbbs.com:24554  172.105.106.228 Error: Socket read error.
1:134/303       bbs.canerduh.com:24554  2604:3d09:227b:26af:19:a08b:78ab:5e16   Error: Connection timed out
1:134/303       bbs.canerduh.com:24554  24.64.95.197    Ok.


Bye, Wilfred.

--- FMail-lnx64 2.2.0.0