I often experience wildly fluctuating latency. I’m not sure if I did this right. I ran Looking Glass but I don’t know how to read it.
TRACEROUTE:
traceroute to 71.226.123.80 (71.226.123.80), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.392 ms 0.379 ms 1.220 ms
2 24.105.18.131 (24.105.18.131) 0.542 ms 0.615 ms 0.700 ms
3 137.221.105.16 (137.221.105.16) 0.918 ms 0.934 ms 0.991 ms
4 137.221.66.18 (137.221.66.18) 25.053 ms 25.059 ms 25.059 ms
5 137.221.83.66 (137.221.83.66) 5.863 ms 5.950 ms 5.960 ms
6 137.221.65.68 (137.221.65.68) 5.682 ms 5.799 ms 5.777 ms
7 137.221.68.32 (137.221.68.32) 12.419 ms 12.433 ms 16.883 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast.net (50.242.151.165) 5.526 ms 5.540 ms 5.597 ms
9 be-11587-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 6.480 ms 6.661 ms 6.527 ms
10 be-7922-ar02.pimaco.az.pima.comcast.net (68.86.93.118) 17.021 ms 17.059 ms 16.813 ms
11 po-1-rur02.orovalley.az.pima.comcast.net (68.87.172.42) 16.999 ms 17.041 ms 16.935 ms
12 68.86.201.2 (68.86.201.2) 17.338 ms 16.984 ms 17.031 ms
13 * * *
14 * * *
15 * * *
03/12/2019 02:05:01 UTC
--------------------
MTR:
Start: Tue Dec 3 02:05:00 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.9 0.8 0.7 1.0 0.0
4.|-- 137.221.66.18 0.0% 10 1.1 7.0 0.9 58.7 18.2
5.|-- 137.221.83.66 0.0% 10 5.8 8.3 5.8 23.9 5.7
6.|-- 137.221.65.68 0.0% 10 59.1 11.8 5.6 59.1 16.7
7.|-- 137.221.68.32 0.0% 10 6.0 8.3 5.9 28.4 7.0
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 5.7 5.7 5.6 6.0 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 7.5 7.1 6.2 8.2 0.5
10.|-- be-7922-ar02.pimaco.az.pima.comcast.net 0.0% 10 16.8 17.0 16.8 17.3 0.0
11.|-- po-1-rur02.orovalley.az.pima.comcast.net 0.0% 10 17.1 17.1 17.0 17.3 0.0
12.|-- 68.86.201.2 0.0% 10 17.2 17.1 17.1 17.3 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
03/12/2019 02:05:00 UTC
--------------------
1 Like
Hey, yessquire! The looking glass here appears fine in the connection. This tests the connection from the Blizzard servers to the computer. To compare the tests with the connection from the computer to us, could you run a WinMTR test while the fluctuating latency occurs for 10-15 minutes?
It seems to run well during the day or late at night. I will try it this evening (I’m in AZ), when I start getting 1k+ms latency swings.
Thanks, yessquire! Seems like this might be a peak latency issue. We have seen quite a few Oceanic and Asia players reporting high latency recently. We’ll keep track of any trends we’re seeing for now! Thanks again 
I tried to run the test at around 7PM MST. I couldn’t even play for 2 minutes, much less 15. Disconnects, ServerBusy error, Unable to load License error. Map elements disappearing. Same thing happened last night around this time. This was all I could get:
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.routerlogin.com - 13 | 287 | 251 | 0 | 55 | 3569 | 10 |
| 96.120.59.137 - 9 | 314 | 286 | 9 | 107 | 4964 | 84 |
|po-301-1204-rur02.orovalley.az.pima.comcast.net - 12 | 294 | 261 | 9 | 91 | 4936 | 170 |
| be-5-ar02.pimaco.az.pima.comcast.net - 10 | 311 | 282 | 10 | 125 | 4996 | 24 |
|be-33653-cr02.losangeles.ca.ibone.comcast.net - 10 | 311 | 281 | 23 | 95 | 3700 | 59 |
|be-11587-pe02.600wseventh.ca.ibone.comcast.net - 10 | 312 | 282 | 21 | 96 | 2296 | 105 |
| Destination host unreachable. - 11 | 304 | 272 | 24 | 251 | 2470 | 169 |
| ae1-br02-eqla1.as57976.net - 11 | 298 | 268 | 22 | 300 | 4936 | 728 |
| be2-pe01-eqla1.as57976.net - 10 | 307 | 278 | 23 | 244 | 4254 | 217 |
| lax-eqla1-ia-bons-02.as57976.net - 9 | 310 | 283 | 22 | 301 | 4445 | 709 |
| 24.105.30.129 - 10 | 300 | 270 | 24 | 238 | 4903 | 472 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I thought it cleared up an hour later, but alas no.
This is a 15 minute test at 9:15 MST
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.routerlogin.com - 10 | 655 | 592 | 1 | 96 | 2202 | 2 |
| 96.120.59.137 - 8 | 693 | 639 | 10 | 111 | 2011 | 12 |
|po-301-1204-rur02.orovalley.az.pima.comcast.net - 11 | 639 | 572 | 10 | 107 | 2819 | 21 |
| be-5-ar02.pimaco.az.pima.comcast.net - 8 | 691 | 637 | 11 | 117 | 2658 | 31 |
|be-33653-cr02.losangeles.ca.ibone.comcast.net - 9 | 685 | 630 | 22 | 133 | 2359 | 29 |
|be-11587-pe02.600wseventh.ca.ibone.comcast.net - 9 | 685 | 629 | 21 | 119 | 2144 | 28 |
| 50.242.151.166 - 8 | 690 | 637 | 23 | 255 | 2380 | 104 |
| ae1-br02-eqla1.as57976.net - 6 | 726 | 683 | 24 | 266 | 2930 | 44 |
| be2-pe01-eqla1.as57976.net - 7 | 709 | 660 | 23 | 242 | 2297 | 61 |
| lax-eqla1-ia-bons-02.as57976.net - 7 | 716 | 670 | 22 | 256 | 2381 | 67 |
| 24.105.30.129 - 8 | 696 | 644 | 23 | 247 | 2835 | 67 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| 192.168.100.1 | 0 | 48 | 48 | 0 | 0 | 0 | 0 |
| 192.168.1.1 | 0 | 48 | 48 | 0 | 0 | 2 | 1 |
| 100.73.0.1 | 0 | 48 | 48 | 1 | 4 | 20 | 2 |
| 122.2.206.82.static.pldt.net | 0 | 48 | 48 | 2 | 2 | 4 | 3 |
| 210.213.131.66.static.pldt.net | 0 | 48 | 48 | 2 | 5 | 39 | 3 |
| 210.213.128.117.static.pldt.net | 0 | 48 | 48 | 3 | 35 | 118 | 11 |
| 210.213.133.109.static.pldt.net | 0 | 48 | 48 | 2 | 3 | 16 | 3 |
| 203.131.251.161 | 0 | 48 | 48 | 28 | 29 | 33 | 29 |
| ae-4.r02.tkokhk01.hk.bb.gin.ntt.net | 15 | 28 | 24 | 139 | 144 | 148 | 148 |
| r4003-s2.tp.hinet.net | 20 | 25 | 20 | 160 | 170 | 179 | 166 |
| r4103-s2.tp.hinet.net | 30 | 20 | 14 | 163 | 167 | 171 | 168 |
| tpdt-3022.hinet.net | 20 | 25 | 20 | 0 | 169 | 174 | 168 |
| tylc-3032.hinet.net | 35 | 20 | 13 | 0 | 170 | 174 | 172 |
| tyfo-3301.hinet.net | 20 | 25 | 20 | 0 | 170 | 174 | 163 |
| 210-65-126-65.HINET-IP.hinet.net | 20 | 25 | 20 | 0 | 171 | 176 | 167 |
| 210.242.32.201 | 35 | 20 | 13 | 0 | 171 | 175 | 173 |
| 210.242.246.53 | 21 | 24 | 19 | 0 | 169 | 175 | 172 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
| No response from host | 100 | 9 | 0 | 0 | 0 | 0 | 0 |
same here. I’m from Philippines and there’s no time that lag stops!
the server is getting worst.
1 Like
I can sympathize with your plight, however, it would have been better if you had made your own thread.
Your first hop (router) is terrible. 13% data packet loss, average 55, worst 3569!
I’d power it off for 10 minutes to see if it will clear things up.
Good luck.
I expect to get a certain amount of lag/latency because I am forced to use wifi.
However, at 3PM it was <200ms, as it is now at 10:30PM. At 7PM it was unplayable with spikes from 1100 to 1700 ms. I don’t think this is my router taking a dinner break:)
edit: This router is only 2 weeks old and the problem just started yesterday.
Wifi uses radio wave, more precisely microwave which also used by phones.
It may be interfered easily. At peak hours, your neighbors get home and switch on their wifi router, watching Netfix, playing mobile games, …
The air might filled up with radio waves…
If possible, try wired connection as a comparison. Or, try other wifi channel on the settings.
Mask is right though. From the data you posted you are getting 13% packet loss at that hop. That is enough to totally trash your gaming, or a lot of other things that don’t buffer. Even a couple % packet loss will make real time applications like online gaming an issue.
I would start with his suggestions and power cycle the connection. It won’t hurt anything, and is the first troubleshooting step when you have that kind of packet loss. Blizzard Support - Power Cycling Your Network Devices
Wired is the next step to try after that. If wired helps, you know it is something related to the wireless aspect.
From looking at your data, you are having issues with the middle part of your routing. This is not uncommon. It is where your data goes through the submarine cables which are often broken or under repair.
This is where things go bad. See the 15% data packet loss there? That first number represents how many data packets are being dropped.
Have you tried connecting to the Americas servers located in Australia? It would change your routing path, hopefully, and you might get more stable results.
Selecting a Server in Diablo 3
Original Author: Narull
Updated with intro and SA information by: MissCheetah
By default the game will place you on the server closest to you geographically. Sometimes you may want to force the game to play on the server of your choice instead, either for matchmaking or performance. Narull provided great instructions and screen captures.
- Close Diablo III and open the launcher, click the little arrow up the top left and select ‘Settings’:
- In the new window select ‘Game Settings’:
- Tick the box for ‘Additional command line arguments’ and in the new command line put the following:
If you want to always connect to the US Server in Los Angeles: OnlineService.Matchmaking.ServerPool=Default
If you want to always connect to the ANZ Server: OnlineService.Matchmaking.ServerPool=AU1
If you want to always connect to the South America Server: OnlineService.Matchmaking.ServerPool=SA1
So it should look like this:
Imgur: The magic of the Internet
Click ‘Done’ and run Diablo III, BAM done! It’s that simple.
I approve that last 2 days diablo 3 is has really high network latency. What ip should I check for Russia servers?
The IP can be found in the support article:
You can use 185.60.112.157 for EU server.
FYI, I have been playing on EU server for over 30 hours in S19, and didn’t experience any problems. Go ahead for a WinMTR test. See if we can locate your problem.
For the record, it was much better tonight.
Something you might want to do, yessquire, is make sure your router’s firmware is up to date. A lot of routers, especially Cisco (Linksys) models, have issues with the Battle.net infrastructure for some reason until their firmware is updated.
But I do have to say that regardless of your firmware, any packet loss on at the router itself indicates a problem that needs to be resolved. Otherwise you’re going to end up with game problems no matter where you connect to online.
Thank you all for the responses.
I still get lag spikes during peak hours, but my hop to the router is down to less than 3% loss. Cycling did not change anything, but DNS flush seems to have fixed that part.
As to firmware, Netgear took care of updates through the Blackhawk App when I installed and set up the router.
