High World MS since a week or so

Support Technical Support
1

Greetings. Been reading a bit on this and seems a bunch of people have been experiencing this as well. However, it seems like a common theme for others has been Dallas or Level3 something hops. I’m not quite sure how to read my tracerts or anything, but I don’t think I"m hitting those.

Here’s the traceroute to US Central Blizz

    Tracing route to 24.105.62.129 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1 
  2     1 ms     1 ms     1 ms  104-222-109-1.dyn.celerity-dtv.net [104.222.109.1] 
  3     3 ms     4 ms     2 ms  ge1-45.royalpalm-sw1.celerity-dtv.net [104.222.104.41] 
  4     5 ms     4 ms     5 ms  vlan408.core1.mia2.celerity-dtv.net [104.222.104.97] 
  5     5 ms     5 ms     5 ms  170.55.61.41 
  6     6 ms    10 ms     6 ms  208.67.164.157 
  7    13 ms     5 ms     8 ms  198.32.125.224 
  8    50 ms    47 ms    47 ms  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
  9     *       71 ms    56 ms  xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50] 
 10    45 ms    80 ms   160 ms  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 11    47 ms    46 ms    48 ms  be2-pe01-eqch2.as57976.net [137.221.69.71] 
 12    50 ms    50 ms    51 ms  chi-eqch2-ia-bons-02.as57976.net [137.221.66.11] 
 13    48 ms    50 ms    48 ms  24.105.62.129

This is the WINMTR with me mid-raid.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |  529 |  529 |    0 |    0 |    6 |    0 |

|      104-222-109-1.dyn.celerity-dtv.net -    0 |  529 |  529 |    0 |    3 |  164 |    0 |

|   ge1-45.royalpalm-sw1.celerity-dtv.net -    0 |  529 |  529 |    1 |    3 |   23 |    1 |

|     vlan408.core1.mia2.celerity-dtv.net -    0 |  529 |  529 |    4 |    8 |  624 |    4 |

|                            170.55.61.41 -    1 |  524 |  523 |    4 |   71 | 1396 |    5 |

|                          208.67.164.157 -    0 |  529 |  529 |    4 |    9 |  630 |    4 |

|                          198.32.125.224 -    0 |  529 |  529 |    4 |    8 |  616 |    5 |

|              ae1-br01-eqmi2.as57976.net -    1 |  526 |  525 |   46 |   53 |  769 |   47 |

|       xe-0-0-0-1-br01-eqat2.as57976.net -    8 |  414 |  385 |   46 |   50 |  355 |   47 |

|         et-0-0-4-br02-eqch2.as57976.net -    1 |  526 |  525 |   37 |   44 |  762 |   38 |

|              be2-pe01-eqch2.as57976.net -    1 |  526 |  525 |   45 |   50 |  766 |   46 |

|        chi-eqch2-ia-bons-02.as57976.net -    1 |  526 |  525 |   48 |   52 |  769 |   48 |

|                           24.105.62.129 -    5 |  450 |  430 |   46 |   48 |  358 |   47 |

|________________________________________________|______|______|______|______|______|______|

Went back and did a tracert for west coast blizz IP as well just in case…

Tracing route to 37.221.105.2 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1 
  2     1 ms     1 ms     1 ms  104-222-109-1.dyn.celerity-dtv.net [104.222.109.1] 
  3     1 ms     2 ms     1 ms  ge1-45.royalpalm-sw1.celerity-dtv.net [104.222.104.41] 
  4     6 ms     5 ms     4 ms  vlan408.core1.mia2.celerity-dtv.net [104.222.104.97] 
  5   395 ms     6 ms     7 ms  170.55.61.41 
  6     5 ms    17 ms     5 ms  208.67.164.157 
  7     7 ms     6 ms     6 ms  be-115-pe01.nota.fl.ibone.comcast.net [50.242.148.157] 
  8     6 ms     6 ms     5 ms  50.248.117.198 
  9   128 ms   127 ms   129 ms  ash-bb4-link.telia.net [62.115.120.176] 
 10   134 ms   134 ms   135 ms  nyk-bb4-link.telia.net [62.115.136.200] 
 11   128 ms   129 ms   128 ms  kbn-bb4-link.telia.net [80.91.254.90] 
 12   129 ms   127 ms   129 ms  kbn-b2-link.telia.net [62.115.123.193] 
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *

Please provide any assistance possible. Also think it’s weird I’m going the tracert is going to the west coast IP when I’m east coast and play on Gorefiend which I thought was an east/central server. Maybe I should be doing to west coast IP?

This all happened about a week ago. I’ve done power cycling router… flushing the goods… resetting UI… I’m always on Ethernet, etc. I’m all out of ideas at this point.

Thanks in advance for your time!

2

Just popping in to say that my West Coast traceroute looks very similar to yours. I started having issues last Wednesday–my world ping hit a whopping 18k right smack in the middle of my guild’s Uldir achieve run. I figured it was a fluke and bowed out.

Showed up for raid night tonight . . . no dice. The game was unplayable. I hit over 10k world ms on Taloc’s elevator and got sliced up by laser beams I couldn’t see.

I don’t have any fixes, just posting here in support! You’re not alone in this, aggravating as it is.

1 Like
3

Having this same issue on a fiber-optic connection… Home MS and other games are sub 60 ms. World MS shoots up to almost 5000 when we were pulling Mythic Mythrax.

4

Your 9th hop on the report shows an asterix it also shows the most lost packets on your WinMTR report. this could be your issue. You should contact customer support and see what they can suggest the more people who contact them with this issue the faster they can fix it. For the meanwhile you can look into VPN services there are a few free ones out there which will allow you to play with a slightly higher MS but at least playable until blizzard can get this resolved.

I tried windscribe VPN 15GB for free lastnight and didnt have the massive 4k world latency and almost killed Fetid mythic those 1% wipes yikes. You could try that and see if it helps for now until blizzard can fix it.

9 * 71 ms 56 ms xe-0-0-0-1-br01-eqat2.as57976. net

8%loss
| xe-0-0-0-1-br01-eqat2.as57976. net - 8 | 414 | 385 | 46 | 50 | 355 | 47 |

5

I have the same issues as this, mostly when I enter a battleground or a raid where multiple actions are taking place

6

Same to US central servers mostly Level3 in Dallas where is I am experiencing high packet loss.

7

Geez, a few replies to other people that have the whole Level 3 thing in their tracert, but I don’t see that in mine so is it part of that known issue?

8

Started on my server in raids/ instances

9

Same issue. Getting 6k MS on Ghuun, and 9.5k ms in RBGS… I play on Tich if that matters. Unplayable.

10