It appears to be back to normal. Maybe it was just a hiccup in the servers.

I hope your issue is solved now. :-) And I have no idea where this issue caused from. If it happens again, please let me know.

It's happening again. Same issue, it's as if I'm playing at 500ms+ on every Node but when I disable mudfish it goes back to normal.
I'm pinging normally to google and on there seem to be no issues on the nodes' status page either. I'm lagging only in-game and when mudfish is on, regardless of the node I'm using.

EDIT: It fixed itself again, it lasted about half an hour. Very weird.

If you're familiar to use PingPlotter (http://pingplotter.com/) or WinMTR, please keep test against 64.25.35.100 IP (game server IP) address to see which hops are causing this problem when you encounter this weird problem. After that, please let me know its result. :-)

I'm getting a "No response from host" on 64.25.35.100 on both programs. IPs like the Node's ones work.

Then try to 64.25.35.1 instead of 64.25.35.100. Here is my result from traceroute:

$ traceroute -n 64.25.35.1
traceroute to 64.25.35.1 (64.25.35.1), 30 hops max, 60 byte packets
1 10.7.64.1 0.332 ms 0.321 ms 0.350 ms
2 10.4.252.10 0.269 ms 0.288 ms 0.295 ms
3 64.235.157.4 0.523 ms 0.543 ms 0.462 ms
4 64.235.159.254 1.451 ms 1.538 ms 1.633 ms
5 209.222.84.25 1.251 ms 1.289 ms 1.268 ms
6 216.129.118.49 1.562 ms 1.513 ms 1.528 ms
7 69.36.239.151 2.396 ms 2.465 ms 2.498 ms
8 208.76.187.68 2.544 ms 4.188 ms 4.105 ms
9 208.185.155.93 2.008 ms 3.610 ms 2.731 ms
10 64.125.28.1 1.764 ms 2.598 ms 2.565 ms
11 64.125.13.242 2.614 ms 2.746 ms 2.720 ms
12 * * *
13 64.25.35.1 41.566 ms 41.490 ms 41.552 ms

https://i.gyazo.com/f4173a726d35af337abc7c47d78e7db6.png

Samething with 64.25.35.1

Um. It means that you're under network firewall and it blocks ICMP or UDP protocol used by pingplotter to check its status. :-( Are you using mudfish at company, school or etc where network firewall exits?

I'm using it at home. It pings normally with the Nodes' IPs/google/etc, but I can't make this one you sent me to work.

Interesting.. You mean that you can't send pings to 64.25.35.100 IP even if it ran from Command Prompt?

At my side, I can normally send a ping to it as follows:

$ ping 64.25.35.100
PING 64.25.35.100 (64.25.35.100) 56(84) bytes of data.
64 bytes from 64.25.35.100: icmp_seq=1 ttl=242 time=42.6 ms
64 bytes from 64.25.35.100: icmp_seq=2 ttl=242 time=42.6 ms
^C
--- 64.25.35.100 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 42.652/42.665/42.678/0.013 ms

If it's really true, it means something at middle of your network intercepts your packets.

I tried disabling my firewall. It works and it doesn't. The ping it shows is "<1ms" which is really weird.

Anyway to get rid of this thing in the middle of my network?

Good to hear that it's caused by your firewall. Then try it again after turning off FastConnect mode. With that it should work. FYI at next package release, this issue should be removed.

https://i.gyazo.com/13fb1731a143bc117537d92c47ef4c63.png

This is with firewall disabled + fast connect disabled.
I am no expert but something seems to be wrong, is it on my end?

Which mudfish node did you use when you performed this test? At hop 3, already packet loss rate was about 15% (huge!). It means there's some problems to communicate with mudfish node you'd picked. Please check the public IP of mudfish node at http://en.loxch.com/servers.php and test against to mudfish node's public IP again to know why this hugh packet loss happens.

However regarding to ping and RTT, it seems find because based on this information you're currently playing at 48 ms.

-Firewall disabled
-FastConnect disabled
(Not possible to ping the game's server ip without disabling these)
  
Alright here are some samples:
  
First one: Pinging the game server IP while connected through the Node CA East (Montreal - OVH 2).
https://i.gyazo.com/7cf728be3dea6a264f6e52c8e8d48e8d.png  
  
Second one: Pinging the IP of Node CA East (Montreal - OVH 2) itself.
https://i.gyazo.com/c7ceac009675978b1928cc6936bfc550.png  
  
Third one: Pinging the game server IP while connected through the Node CA East (Montreal - LunaNode).
https://i.gyazo.com/659d9d6fd22eb3f5e0abc8fd4760c89b.png  
  
Fourth one: Pinging the IP of Node CA East (Montreal - LunaNode) itself.
https://gyazo.com/5042a6992a7d53d477bf6e906fbcf7a4
  
Any procedures I should take to fix this? Will I have to change my internet provider?
  
  
  

           I can ping to the game's server ip with my firewall and fast connect enabled now. The error from before disappeared. However the results are the same. When connected through the 2 Nodes I still get 100% loss on 2 addresses.
  
EDIT: Pinging to the game's server IP while connected through CA East (Toronto - DigitalOcean).
https://i.gyazo.com/11d7f1147fecfb17274ca09fa1b8da88.png  
  
Apparently I only get 100% loss on 2 addresses on the 2 Montreal Nodes I use.

>  I can ping to the game's server ip with my firewall and fast connect enabled now. The error from before disappeared. However the results are the same.    
    
This might be fixed by upgrade the version to v4.3.18.    
    
> When connected through the 2 Nodes I still get 100% loss on 2 addresses.      
    
Thank you for detailed update from First to Fouth.  According to your last images I'd checked, it's all good.  And you can ignore any hops whose packet loss is 100% and it's safe to be ignored because its routers block ICMP protocol.  I think your issue might happen or not based on time.  Please try to keep this test when you encounter packet loss issue again.  
    

Yes, I have not had any issues with the Nodes recently even though I get 100% loss on some hops.
  
You are always the one answering my questions, thank you for being so helpful (:

:-) Yes it should okay because based on your graphs it seems the connection is clean and stable.  
  
If there are other issues, please let me help you again.