K0STK

This appeared on Facebook regarding the IT situation over at the ARRL:

This was reported by Chris NW6V

Mike Ritz, W7VO, ARRL 2nd Vice President, was at the WVDXC club meeting last night, having just attended an ARRL board meeting to discuss the outage. Mike reported those meetings are a weekly event until the matter is resolved.

Everything that was running on INTERNAL servers is down until further notice. That includes their VoIP phone system, their .org email addresses, and front ends for things like LOTW. Everything running on external servers - cloud servers etc. - including LOTW data, is believed unaffected. But, such data will not be available until the internal matters are resolved. Thus, "[email protected]" doesn't work - because that was on their internal mail server. But "[email protected]" does - because the relays didn't run internally. I checked, and [email protected].

Efforts to restore the internal systems is proceeding full-time. No time-line can be given. The nature of the problem cannot be discussed.

I believe Mike said - with air asterisks around his words - "We have been advised to say nothing." He responded similarly when asked if "the Feds" were investigating this.

READ MORE: https://w2lj.blogspot.com/2024/05/interesting-speculation.html

On Thursday, January 18th, I discovered that the Winlink APRSLink callsign is now WLNK rather than WLNK-1.

Here's how ...

My APRSLink login attempt through WLNK-1 (over VHF) failed so I switched to APRSDroid (over TCP/IP) to rule out an iGate/digi issue.

When I started APRSDroid I received a "message waiting" notice from WLNK instead of the expected WLNK-1.

So I sent my APRS messages to WLNK and was able to login over both VHF and TCP/IP.

This callsign change has not been mentioned at https://winlink.org/APRSLink