[aprssig] third.aprs.net issues

Heikki Hannikainen hessu at hes.iki.fi
Wed Aug 17 08:32:04 EDT 2022

Oops, fixed. Seems like aprsc actually bugged in this container 
environment - after reboot it failed to listen on the UDP port.

I need to set up an automatic alert for this.

Thanks for the note!

On Tue, 16 Aug 2022, Lynn W Deffenbaugh (Mr) wrote:

> Turns out it's even more easily seen if you scroll down to the Peers 
> section.  It appears that third.aprs.net has not received any inbound packets 
> from any of its peers for the past 31 DAYS! This has apparently been going on 
> for quite some time.
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> On 8/16/2022 10:48 AM, Lynn W Deffenbaugh (Mr) wrote:
>> I sent a direct message to Hessu who manages this server, but thought the 
>> rest of the APRS community might want to know there's an issue happening.
>> I had occasion to notice that my ANSRVR is having some response issues this 
>> morning and tracked it down to third.aprs.net.  This core server doesn't 
>> seem to be getting a full feed from the APRS-IS at this point in time.
>> You can see this by opening browser windows to the first 3 aprs.net server 
>> status pages.  Wait for them to start updating and look at the rate of 
>> "Unique packets seen" under the "Duplicate filter" section.  On first and 
>> second, this rate is 70+/second, but it's <6/sec on third indicating that 
>> not all of the APRS-IS traffic is getting processed by this server.
>> http://first.aprs.net:14501
>> http://second.aprs.net:14501
>> http://third.aprs.net:14501
>> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

   - Hessu

More information about the aprssig mailing list