What is your average in-game latency with DMZ.MY?

I’m collecting some information on your experience with DMZ.MY and I would appreciate it if you can let me know what is your average in-game latency when you’re connected to our DMZ.MY servers.

Please help me by voting on the poll below. Thank you very much.

DMZ.MY Servers’ Ping Status display

A little history…
We understand that there are times where you’re experiencing lag spikes/high latency even though you’re connected to our DMZ.MY servers. The are 2 reasons for that to happen -

1. Your connection to our DMZ.MY servers is not optimal due to either a local ISP issue or network interruptions.
2. Our DMZ.MY servers itself is experiencing a higher latency issue due to network interruptions.

For Issue no. 1, it is very easy to troubleshoot as running a simple ping test from your PC to our servers will be able to help you identify if there is any packets loss or it’s showing ping results which is higher than usual.

But for Issue no. 2, you have to contact us to find out if the servers are working fine and if the network link on the servers itself is having some issue.

Our solution
We have now added a new ‘Servers Status’ tab in our Members Portal.

This ‘Servers Status’ tab loads all ping test results generated by our DMZ.MY servers (automatically every 10 minutes) and display them back to you. From this results, you will be able to identify if our servers are working optimally in order to help troubleshoot your situation.

This will also help you identify which other servers are performing well and assist you in quickly choosing an alternative server to connect to.

New ‘Servers Status’ display
Here’s an overview on how to read the ping results and identify if there is any issues with our servers.

1. All the ping results retrieved from the Servers will have a timestamp to show at what time the test is executed. This timestamp is set to UTC format.
2. This is the ping response results from the LA WoW datacenter (IP 12.129.193.242). Basically, the lower the number the better but it should also be almost consistent to ensure a stable connection.
3. This shows how many ping requests were sent and how many requests were replied. If there are any packet loss, then this might result in lag spikes and higher latency to your gameplay.

 

This is just one of our many efforts to help improve your gameplay experience with DMZ.MY. We welcome any feedback or suggestions in order to help improve our service better. Please contact us via the Support channels listed in the Members Portal.

Thank you.

MAL04 current status

Dear valued users,

There was an interruption yesterday to MAL04′s network route that resulted in slightly degraded performance. While it is not a total disruption; I believe some users experienced a higher latency when connected to MAL04.

Since this is out of my control, I’ve only been able to closely monitor it’s status. It seems that now, all previous issues with regards to the earlier issue has been resolved.

This is the current ping time from MAL04 to LA WoW datacenter:

PING 12.129.193.242 (12.129.193.242) 56(84) bytes of data.
64 bytes from 12.129.193.242: icmp_seq=1 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=2 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=3 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=4 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=5 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=6 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=7 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=8 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=9 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=10 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=11 ttl=243 time=209 ms
64 bytes from 12.129.193.242: icmp_seq=12 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=13 ttl=243 time=211 ms
64 bytes from 12.129.193.242: icmp_seq=14 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=15 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=16 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=17 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=18 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=19 ttl=243 time=208 ms
64 bytes from 12.129.193.242: icmp_seq=20 ttl=243 time=210 ms

— 12.129.193.242 ping statistics —
20 packets transmitted, 20 received, 0% packet loss, time 19009ms
rtt min/avg/max/mdev = 208.293/208.847/211.392/0.885 ms

It’s back to it’s normal 200~ms range and very constant.

My apologies for any inconvenience caused and please contact me via the Support channel should you require further assistance.