Diablo 3 connecting overseas

For some reason, my d3 client is creating games on a german IP (37.244.30.131). I am playing from canada, connecting to the americas according to the battlenet options.

I am experiencing quite a bit of latency, despite my fibre connection. My computer is more than capable of running d3 on max, yet this lag persists even when I am on low settings, so it is not machine related.

any ideas how I can get a connection to a server on this continent?

WINMRT
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            Cogeco.local -    0 |    8 |    8 |    0 |    9 |   14 |   12 |
|                             10.75.224.1 -    0 |    8 |    8 |    7 |    9 |   11 |    8 |
|                             10.0.68.149 -    0 |    8 |    8 |   21 |   24 |   26 |   21 |
|                              10.0.18.78 -    0 |    8 |    8 |   20 |   24 |   30 |   20 |
|                              10.0.18.29 -    0 |    8 |    8 |   21 |   29 |   34 |   21 |
|                            4.59.214.145 -    0 |    8 |    8 |   24 |   27 |   30 |   24 |
|                            4.69.142.178 -   34 |    3 |    2 |    0 |   38 |   39 |   38 |
|    BLIZZARD-EN.ear7.Chicago2.Level3.net -    0 |    8 |    8 |   35 |   39 |   61 |   35 |
|              ae1-br01-eqch2.as57976.net -    0 |    8 |    8 |   85 |   95 |  149 |   85 |
|                          137.221.65.132 -    0 |    8 |    8 |   80 |   83 |   86 |   85 |
|         et-0-0-2-br01-eqla1.as57976.net -    0 |    8 |    8 |   80 |   86 |  113 |   81 |
|              be1-pe02-eqla1.as57976.net -    0 |    8 |    8 |   82 |   84 |   86 |   86 |
|        lax-eqla1-ia-bons-03.as57976.net -    0 |    8 |    8 |   84 |   85 |   87 |   84 |
|                           24.105.30.147 -    0 |    8 |    8 |   83 |   84 |   87 |   85 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    1 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|

Sometimes the IPs are re-used and assigned to a different location. It means when you look it up, you get the wrong info.

You appear to be going through Chicago on Level3 services and right before that you have 34% packet loss. That would cause the issues you are seeing.

After Chicago I am guessing you get routed to the LA California data center. I really don’t think you are going to the EU.

Have you tried a VPN to change your route to Blizz? If you can avoid that hop that has 34% packet loss you may have much better results.

Edit - also when you test using WinMTR, let it run for a good 10 mins when you are having an issue. You let it run for seconds so you only sent 8 data packets. That gives you a TINY snapshot of a window to look at results. You want results over time to look for patterns that persist.

1 Like