Echolink Error in parsing header

one of the ASL/Echolink nodes I manage is not showing online on Echolink today seems like a recent development.
I rebooted the node a few times trying to see if it would resolve but no go.

Here’s a screenshot of the asterisk logs. do i need to change servers or is echolink having an issue?

from echolink.conf:
server1 = nasouth.echolink.org
server2 = naeast.echolink.org
server3 = server3.echolink.org

Well i changed my echolink servers to this and rebooted and it appears to be working again.

server1 = server1.echolink.org
server2 = server3.echolink.org
server3 = server6.echolink.org

I’ll keep an eye on it.

Outside of logging in via wifi in the same NAT/ext-IP on a phone, you probably hit the cause as the second largest reason for it.

It happens from time to time. I keep them all listed and comment them out when there is a issue.
It will start with the first on the list and move through it until it gets a reply up to 3. Then back to top of list.
So, you do need to allow a little time as it tries each as well. Not sure how long.

I would double check router firewall settings. Make sure UPD ports 5198 & 5199 are routed to your device.