If the issue is with the upper ISP or the destination side, why are IPs like 103.157.33.90 and 156.59.92.166 able to hit 0-2ms from the same Mudfish node?
They are also part of the same game/provider infrastructure (Zenlayer/Jakarta). This suggests that a direct path exists, but these specific CIDR blocks are just not assigned to it yet.
Please try to re-route them through the same upstream provider used by the 2ms IPs. I really appreciate your effort on this.
My apologies, after further testing, I realized these specific IPs are physically located in Singapore. The 14ms RTT from Jakarta node is already optimal and correct. Please disregard my previous request regarding these blocks. Thanks for your help!
1 Like
After a deeper trace and further verification, I found that some of these CIDR blocks are physically routed through Singapore, which explains why they stay at 14ms from the Jakarta node. My bad for the oversight on the physical location of those specific IPs.
You can close this ticket for now as 14ms is indeed the optimal path for these Singapore-based routes.
However, I will keep monitoring the network. If I find any other IPs physically located in Jakarta that are still showing high RTT, I will report them back to you immediately.
Thanks for the support..!!
Cool! 
I hope now everything goes well with mudfish. Please let me know if there are any other problems.
1 Like