MSGID: 2:221/6.0 619452a8
PID: SmapiNNTPd/Linux/IPv6 1.3 20211030
EID: ..
CHRS: UTF-8 4
TZUTC: 0200
TID: hpt/lnx 1.9.0-cur 2021-10-08
I forgot to add a few more of his comments:

"The odd thing is that when you look at the statistics panel for VE3FOY-3 on
this website, there are lots of other APRS nodes receiving what it transmits,
but NONE listed that are heard by this digipeater.

"That could mean that this digipeater has no receiver OR a broken RF receive
path, OR simply has not heard any other APRS nodes (local or remote) because
none have ever entered its RX coverage range this month (ie. all local APRS
traffic was blocked by local hills or the RX antenna is directed at a specific
area or the sky for satellite comms with the ISS).

"I can only guess what info this particular digipeater is transmitting other
that its own position and status. The receiver on this digipeater may be fine,
just awaiting a natural disaster or search and rescue effort in its intended
coverage area to service.

"Sadly the expected coverage area is not announced in its status message. The
APRS nodes that I maintain announce their expected coverage area by indicating
the type and height of the antenna and transmit power level, for instance.

"The callsign seems to be also assoicated with a VHF repeater run by COARC
(Central Ontario Amateur Radio Club)."

"My guess would be that the receive path is temporarily (long term) somehow
broken or noone bothers with APRS there...

"It may still be run by the local ham club, or maybe the digipeater owner now
has a particular purpose in mind that is not publicly announced.
--- 
 * Origin: nntp://news.fidonet.fi (2:221/6.0)
SEEN-BY: 1/123 14/0 30/0 90/1 103/705 105/81 120/340 123/131 129/305
SEEN-BY: 154/10 218/700 221/1 6 226/30 227/114 229/200 424 426 428
SEEN-BY: 229/616 664 700 240/5832 249/206 317 400 261/38 282/1038
SEEN-BY: 301/0 1 101 317/3 322/757 335/364 342/200 633/280 712/848
SEEN-BY: 4500/1
PATH: 221/6 301/1 229/426