Hello, I really really like mudfish. Its really help me in gaming, but lately the SG node is very laggy and giving so many packet loss. I wonder if it’s the node server or its from my end. I usually use Azure 3 and Linode 2 for ArcheAge SEA and it works amazing giving me 23ms from Indonesia while the other Nodes is having 70-250ms and not stable.
Will it possible to add more Node for Singapore Server or something ?
Thank you!
Please try to test your network status from your desktop to 47.88.170.34 (the public IP of SG Asia (Singapore - Aliyun) mudfish node) using How to use WinMTR link.
I think this result shows you where this issue is from. If it points that this issue is from Mudfish side, I’ll try to expand more mudfish nodes at SG.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| gpon.net - 0 | 213 | 213 | 0 | 0 | 13 | 0 |
| 36.69.160.1 - 0 | 213 | 213 | 2 | 4 | 21 | 2 |
| 180.252.1.101 - 0 | 213 | 213 | 1 | 2 | 14 | 1 |
| 101.190.240.180.in-addr.arpa - 8 | 167 | 155 | 16 | 17 | 67 | 16 |
| 101.190.240.180.in-addr.arpa - 7 | 169 | 158 | 15 | 16 | 23 | 16 |
| 49.204.240.180.in-addr.arpa - 0 | 213 | 213 | 16 | 17 | 24 | 17 |
| 38.129-240-180.static.telin.sg - 0 | 213 | 213 | 17 | 18 | 51 | 18 |
| 221.81.251.116.in-addr.arpa - 0 | 213 | 213 | 17 | 18 | 33 | 17 |
| Request timed out. - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| 34.170.88.47.in-addr.arpa - 0 | 213 | 213 | 17 | 18 | 29 | 18 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
Also, whats the IP Public for Linode 2 / Azure 3 ? I want to test that one as well, because I really like that node.
Thanks for the reply!
Thank you for this WinMTR result. When I checked this result, it shows that your packet loss is happening at 101.190.240.180.in-addr.arpa hop so its IP is 180.240.190.101.
If I whoised this IP, it shows its ISP is TELIN-NET-SG and it’s at the upsteam ISP which we could not control to bypass. 
It’s found at https://mudfish.net/server/status link. Please click the mudfish node to see the details.
Linode 2:
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| gpon.net - 0 | 96 | 96 | 0 | 0 | 4 | 0 |
| 36.69.160.1 - 0 | 96 | 96 | 2 | 4 | 23 | 3 |
| 180.252.1.101 - 0 | 96 | 96 | 1 | 2 | 5 | 2 |
| 101.190.240.180.in-addr.arpa - 63 | 27 | 10 | 16 | 18 | 24 | 17 |
| 101.190.240.180.in-addr.arpa - 82 | 22 | 4 | 16 | 18 | 23 | 16 |
| 29.204.240.180.in-addr.arpa - 0 | 95 | 95 | 17 | 17 | 25 | 17 |
| 63949.sgw.equinix.com - 0 | 95 | 95 | 17 | 18 | 23 | 18 |
| 10.209.32.2 - 0 | 95 | 95 | 17 | 18 | 26 | 18 |
| 10.209.35.4 - 0 | 95 | 95 | 17 | 18 | 23 | 18 |
| 10.209.1.113 - 0 | 95 | 95 | 17 | 17 | 24 | 17 |
| li1643-216.members.linode.com - 0 | 95 | 95 | 17 | 18 | 24 | 18 |
|________________________________________________|______|______|______|______|______|______|
Azure 3:
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| gpon.net - 0 | 120 | 120 | 0 | 0 | 7 | 0 |
| 36.69.160.1 - 0 | 120 | 120 | 2 | 3 | 14 | 3 |
| 180.252.1.101 - 0 | 120 | 120 | 1 | 2 | 6 | 2 |
| 117.255.94.36.in-addr.arpa - 11 | 85 | 76 | 0 | 4 | 18 | 2 |
| 118.255.94.36.in-addr.arpa - 0 | 119 | 119 | 17 | 20 | 59 | 18 |
| ae29-0.icr01.sg2.ntwk.msn.net - 0 | 119 | 119 | 17 | 19 | 46 | 18 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| Request timed out. - 100 | 24 | 0 | 0 | 0 | 0 | 0 |
| 171.169.198.20.in-addr.arpa - 0 | 119 | 119 | 17 | 18 | 32 | 18 |
|________________________________________________|______|______|______|______|______|______|@lyrael Thank you for these results too. If I checked this result properly, it seems
These IPs are all the public IPs of the upsteam ISPs. So it’s not easy to control this issue.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.