John,

I have had all kinds of issues with Echolink’s nameservers in the last several weeks.  I used to use server1, server2, server3, server4.  However, Server2 and Server 3 have same IP address now.  Not sur about all yours below, I didn’t look them up.  However, I am having this issue on items that are regular Echolink as well – especially if coming from an AMPRNet IP address on the 44.x.x.x network.

It's time we all got together and built a user app around Allstar that can replace the Echolink client if you ask me.

Wish I had a solution, but I haven’t found a good one yet.

Mike

Kb8zgl

From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> on behalf of John Rudolph- N2YP <John@n2yp.com>
Reply-To: Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org>
Date: Friday, July 20, 2018 at 4:11 PM
To: "app_rpt-users@lists.allstarlink.org" <app_rpt-users@lists.allstarlink.org>
Subject: Re: [App_rpt-users] Echolink timeout

I've tried pinging them all includeding echolink.org from my node server, my cellphone via WiFi, my cell via Verizon, my laptop and all my pings come back as 10,000+ ms pings or completely lost packets. I'm guessing this is causing the issue. If I use a website to do the ping it goes quick which I find interesting since I've tried it on two different networks, Spectrum-Time Warner and Verizon. Does anyone else this problem when trying to ping echolink? Is it possible it's a regional issue?

I've tried echolink.org, naeast.echolink. org, nasouth.echolink.org, servers.echolink.org, aprs.echolink.org.
John Rudolph
Amateur Radio Op N2YP
Unadilla,NY