TID: FMail-W32 2.1.3.7-B20170919   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: CP850 2   
   MSGID: 2:280/5555 5cc7615c   
   REPLY: 2:203/2 5cc6bf7c   
   Hello Bj”rn,   
      
   On Monday April 29 2019 11:10, you wrote to me:   
      
    BF> From zero to 13 6DWN in just one week. Wazzup? Is this something long   
    BF> overdue perhaps?   
      
   Yes, there is that. I have no pocedure for checking if the nodes in the list   
   are still up. Sometimes I manually take spot checks, but I had not done that   
   in quite some time. So yes, there was overdue maintenance.   
      
   Yesterday evening I had some time and checked them all. I never expected that   
   many. :(   
      
   I had a closer look and could reduce the 6DWN's to 9. Still a lot though. Two   
   could be eliminated due to an errror in binkp.net. For 5020/9696 and 463/877   
   the AAAA record appears in the host name as in the nodelist, but not in   
   binkp.net. Very odd.   
      
   The problem with Jeff Smith's nodes has been solved.   
      
   That still leaves 4 that have stopped advertising an AAAA record, 4 that give   
   a time out on IPv6 and 1 that gives a socket error on unreachable host.   
      
   Let's hope the problems can be fixed.   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MSVC 1.1.5-b20170303   
    * Origin: he.net certified sage (2:280/5555)   
   SEEN-BY: 1/123 15/2 19/10 203/0 221/0 6 226/17 229/354 426 1014 240/5832   
   SEEN-BY: 249/206 317 400 280/464 5003 5006 5555 292/854 310/31 317/3   
   SEEN-BY: 322/757 342/200 393/68 460/58 633/0 267 280 281 410 412 509   
   SEEN-BY: 640/305 1321 1384 712/848 2452/250 3634/12 3828/7 5019/40   
   SEEN-BY: 5020/545 1042 12000 5053/58   
   PATH: 280/5555 640/1384 633/280 229/426