Call of Duty Warzone issues - not loading Asia

#1

I recently purchased a pay per traffic plan for playing Warzone since I receive a high amount of packet loss.
Unfortunately the Asia node for Singapore/Japan does not work for me.
The problem is that the game keeps trying to find a match but does not find one at all.
I think there are newer game servers for Asia region.
I tried to check the packets using Wireshark and found an IP which constantly is a source for the UDP ports that Warzone uses (3074) - 157.175.87.127.
In a custom item, I used 157.175.87.127/24 as the Routing Path.
But automatic search keeps searching for a node with no success.
Could you help by adding this to the Warzone list?

Warzone crashes when Wireshark is running. I start the capture during the game and it stays for only a few seconds. Would it help if I upload a p capture which is that short?

#2

Weird… When I checked the game item, it seems 157.175.87.127/24 is already covered by the mudfish game item. :frowning: Could you please confirm that it’s also same with Full VPN mode enabled?

#3

same issues for me. it worked before but now cant seem to find any match either on asian server or us

#4

@SAi541 Are you meaning that it doesn’t work with Full VPN mode enabled?

#5

didnt test on full vpn yet. unfortunately full vpn is not an option for me cause i have apps eating bandwidth in the background and i also stream. i hope it gets fix soon before season 4 release of cod

#6

I agree with you that Full VPN mode isn’t a proper option for you. However we need to narrow down this issue whether this issue is from the game item of mudfish itself or from other issues.

When you get a chance, please test with it for a moment whether it solves it. If it works fine, I expect I’ll ask some game packets to you to update missing game server IP blocks from the game item. :frowning: Sorry for this inconvenience.

#7

Hi @weongyo

Thanks for the reply. I had tried full vpn. It works for me while connected via full vpn but there is still high packet loss (70-100%). Also most of the time it keeps searching for a match and fails. I tried different nodes with no luck. Not sure which one exactly would work and there are many.

I have a list of IPs that the application connected to in the last month.
Would you be able to add their CIDRs and let me know so I can test?

139-180-151-190.choopa.net
139-180-151-182.choopa.net
139-180-151-181.choopa.net
mw-lobby-1.prod.demonware.net
139-180-151-185.choopa.net
ec2-15-185-220-81.me-south-1.compute.amazonaws.com
ec2-15-185-42-238.me-south-1.compute.amazonaws.com
95.177.172.247
37.244.43.206
139-180-151-180.choopa.net
58cab127.setaptr.net
78.138.126.105
24.105.53.113
24.105.53.91
ec2-157-175-86-136.me-south-1.compute.amazonaws.com
ec2-15-185-197-241.me-south-1.compute.amazonaws.com
ec2-157-175-82-66.me-south-1.compute.amazonaws.com
185.136.168.3
64.46.108.150
185.136.156.183
87.117.239.21
185.225.209.225
95.177.169.209
185.225.209.246

This is not the entire list, I will try and share more in the next post.