Hi Mudfish Support,
I am a user from South Kalimantan, Indonesia. Currently, the “Mobile Legends: Bang Bang” item only provides Singapore destinations.
For users in my region, routing through Singapore significantly increases latency (high ping). However, the game has local servers in Jakarta which provide much better latency for us.
I really like Mudfish’s “pay-per-traffic” system and I would love to recommend this app to my friends and the local community. However, the current routing is still too far and inefficient for us because the Jakarta destination is missing.
Could you please add Jakarta (Indonesia) as a destination for the Mobile Legends item? This would help many players in Indonesia get a better experience.
If you need a specific IP addresses to identify the Jakarta servers, 216.133.157.41
Thank you.
I’ve collected several Jakarta server IPs used by Mobile Legends (Moonton) via Zenlayer/ExitLag:
216.133.157.41
156.59.161.66
103.157.33.35
All these IPs are confirmed as Jakarta destinations. Please update the MLBB item to include these so users in Kalimantan can get better latency.
I would like to add more evidence on why this Jakarta destination is urgent.
As shown in my dashboard screenshot (attached), my Cell phone to Node latency is very good at only 33ms (South Kalimantan to Jakarta). However, because the destination is forced to Singapore, the Node to Item Server latency jumps to a terrible 321ms.
This confirms that the current routing is sent to a very far location instead of staying within Jakarta. Adding the Jakarta destination would fix this instantly. Thank you."
Okay. Based on your IP information, I’d tried to add “Asia (Jakarta)” destination. When you get a chance, please check it again.
Thank you! I have tested the Jakarta destination and it fixed my routing issue. My ping is now very stable. I will definitely recommend Mudfish to my friends in the local community here. Great job!
Hi again, I found more complete IP ranges to further optimize the Asia (Jakarta) destination and fix the routing inconsistency (sometimes it still jumps to 60ms), I have gathered the complete IP Ranges (CIDR) used by Moonton/Mobile Legends in Jakarta.
Please add all these ranges to the Jakarta destination item:
Zenlayer Jakarta (Major Battle Servers):
103.157.33.0/24
216.133.157.0/24
23.248.170.0/24
23.248.163.0/24
ByteDance / BytePlus Jakarta / Moonton all subnet:
202.52.240.0/21
156.59.0.0/16
Alibaba Cloud (Aliyun) Jakarta:
47.236.0.0/16
161.117.0.0/16
Additional Local Jakarta Peers:
103.157.32.0/24
101.255.0.0/16
Adding these broad ranges (CIDR) will ensure that the traffic stays within Jakarta and doesn’t get routed to Singapore by mistake. This will be very helpful for the Indonesian gaming community.
Thank you so much..!
Hi admin, sorry for the additional reply. I just checked my access logs during the 60ms ping spikes and found these additional Jakarta/Regional ranges used by the game. Please include them as well:
103.111.144.0/23 (Cloud Compute Indonesia - Jakarta)
45.121.218.0/23 (G-Core Jakarta)
129.227.0.0/16 (Zenlayer Regional)
161.202.0.0/16 (SoftLayer/IBM - Moonton Central)
Thank you for your patience..!
Thank you so much for providing such detailed and organized information! It’s incredibly helpful for us to have those specific CIDR ranges to ensure the routing stays within Jakarta.
I have just updated the Mobile Legends: Bang Bang item with all the IP ranges you provided, including the Zenlayer, ByteDance, and Alibaba Cloud subnets.
Could you please test it again when you have a moment? I want to make sure those 60ms spikes are gone and that your connection remains stable. If you find any other ranges or have further suggestions, feel free to let me know.
Thanks again for your support and for recommending Mudfish to your community!
Thank you for the quick update, weongyo..! I’m currently away from my stable connection, but I will test it as soon as I get home and let you know the results. I’ll also keep an eye out for any other IP ranges… Cheeeeers..!
Hi weongyo, thx for the update! tested it and it’s great, got like 28-30ms now (prev was 60ms+). feels way lighter tho.
still noticed some random spikes to 100ms for a sec, but hero movement is fine. maybe there are still some hidden IPs out there. i’ll check the logs and let u know if i find more. cheers!
hi weongyo, found some more IPs causing lag spikes: 128.14.110.32 (Zenlayer) and 161.202.212.248 (IBM). they look like SG IPs but had very high traffic during my matches.
fyi, i’m using Jakarta destination in my settings, so these IPs shouldn’t be causing spikes if they’re routed correctly. could u check and add these ranges to the Jakarta routing?
- 128.14.0.0/16 (Zenlayer)
- 161.202.0.0/16 (IBM)
thx again!
Thanks for the previous updates! I found another critical IP range for the Jakarta destination: 103.62.54.0/24.
I’ve performed a traceroute to 103.62.54.198 and it clearly routes through BBIX Jakarta and Tencent’s infrastructure (156.59.150.101). As I am playing from Kalimantan, the ~40ms latency I’m getting is the solid proof that this is a domestic Indonesian route (Jakarta), not Singapore.
Please add this range to the Jakarta destination to ensure we stay on the local path. Thank you n sorry for the spam, I just want to make sure we cover all the bases for the Jakarta routing
No problem. I’d updated the game item based on your information. Please test it again when you get a chance.
Thx a lot for the help..! Just did some tests on the new IPs. Interestingly, both Jakarta n Singapore destinations are showing almost identical RTTs now, around 14-18ms from the Jakarta nodes.
Seems like there’s some major congestion in the Indo region right now, prob due to the ongoing Palapa Ring cable mess that’s still not fixed. I’ll keep an eye on it n let u know if things get better later. Thx again for the hard work!
Hi Weongyo! Still on our mission to fix the Jakarta latency. I found some more ‘leaky’ IPs that need your magic touch…!!
I’ve analyzed the RTT from your Jakarta nodes to various MLBB server IPs. I found a clear routing inconsistency where some IPs show 0-2ms (direct), but many others show 14ms+ (leaking/hairpinning via Singapore).
Simply adding these IPs to the “Jakarta Destination” will not fix the latency if the Routing Policy remains the same. To achieve a stable 0-2ms RTT, please add these CIDR blocks and ensure your Jakarta nodes use local IXP (OpenIXP/IIX) peering instead of international transit:
Target CIDR Blocks for Jakarta Optimization:
148.153.128.0/19 (Major Zenlayer block)
103.155.16.0/24 (Zenlayer)
154.85.90.0/24 (Kaopu)
154.93.119.0/24 (Kaopu)
45.198.7.0/24 (Zenlayer)
103.62.54.0/24 (Zenlayer)
161.202.0.0/16 (IBM/SoftLayer)
Specific IPs identified with 14ms+ leaks:
148.153.145.46,
103.155.16.40,
148.153.165.222,
161.202.212.248,
103.62.54.156,
154.85.90.23,
154.93.119.139,
45.198.7.8.
Please force these blocks to use the direct local path. For users in South Kalimantan, this 14ms difference is critical for a stable gaming experience.
Thank you n let me know if you need more data from my side. Looking forward to your magic touch on these routes! Cheers.
Thank you for this information again. I tried to update the game item based on this. Could you please test it again?
I checked through ping.mudfish.net and the RTT from Jakarta nodes to 103.155.16.40 is still around 12-14ms. This means it’s still routing through Singapore. If it’s already optimized, it should be 0-2ms. Please double check the CIDR routing for Jakarta nodes.
I appreciate the update, but I’m still seeing high RTT on several blocks. To prove that these IPs are physically in Jakarta and should be 0-2ms, I compared them using ping.mudfish.net.
Please look at this comparison:
- The “Correct” Route (Already 0-2ms)
These IPs are working perfectly, proving they are in Jakarta:
156.59.79.98 (Zenlayer) → RTT: 1-2ms from Jakarta Nodes.
103.157.33.107 → RTT: 1-2ms from Jakarta Nodes.
(This is the gold standard we are looking for). - The “Leaking” Route (Still 12-14ms)
These IPs (from the list I sent) are still routing via Singapore despite your update:
103.155.16.40 → RTT: 12-14ms (Verified via ping.mudfish.net)
148.153.x.x blocks → RTT: 13-15ms
45.198.x.x blocks → RTT: 14ms
Since some IPs in the same subnet/provider can achieve 2ms, it proves the 14ms ones are just “misrouted” to Singapore.
Could you please re-check the BGP routing / Static routes for the CIDR blocks I provided? They should all be hitting the local Jakarta peering, not hairpining to Singapore.
Thank you!
Found another one: 162.128.46.216.
I’ve re-checked the CIDR blocks from my previous report and they are still stuck at 12-14ms RTT.
154.93.119.0/24
148.153.128.0/19
103.155.16.0/24
154.85.90.0/24
45.198.7.0/24
103.62.54.0/24
161.202.0.0/16
162.128.46.0/24 (New)
When my connection goes through these IPs, it feels like I’m not using Mudfish at all.
For comparison, these IPs are already optimized and hitting 0-2ms RTT from Jakarta nodes:
103.157.33.90
216.133.157.12
156.59.92.166
Please force those 14ms ‘leaky’ blocks to use the same direct path as the 0-2ms ones. They are clearly still hairpining to Singapore. Thanks
Thank you for this update. I’ll try to fix it but if it’s controlled by the upper ISP side, please note that it’s not fixable at Mudfish server side.