I have never received the eleaf error until the new update, I have seen others experiencing the issue in other code releases. There is potentially a routing issue here, having the end users reconfigure their network is not something you should consider as a work around. We should not have to reconfigure our network as it was working fine with the same configurations in the past. A misconfiguration on the end user could pose a security risk. The new code or the modification to the code has caused us to have trouble getting a functioning server.
My recommendations:
1. If you can reproduce the issue (which you can), I would use an application that could capture your routing calls or web calls.
2. Check if your servers resources are above normal thresholds - cpu, memory, disk
3. Pull all bad servers from load
4. If there is a possibility to roll back to a known good code version I would imagine you end user would appreciate more stability vs features.
My network stats:
200 mbps down, 10 mbps up
Own modem and router with most recent updated
Googles DNS
Hope this help, we really like this game the faster the fix the better for us.