High ping, game unplayable

Support Technical Support
1

For the past few days I suddenly have 500-3500 world ms ping when I log into my characters. Every couple of minutes I get disconnected (WOW51900319) and (BLZ51901016). The game is unplayable at this time as I can’t even accomplish simple tasks like getting around Valdrakken or opening my weekly vaults without stuttering and teleporting around and disconnecting.

I’ve tried a lot of the suggested fixes within these forums and online. I’ve reset my modem several times, reset my network settings/drivers, reset my Cache/Interface/WTF folders and addons, reset my DNS settings. Nothing seems to help at this point.

I’ve seen other’s having the same or similar issues but no blue posts clarifying if its an issue on their end. Seems to only be affecting wow and battle.net app. Other games and devices/videos/streams work just fine for me, no hiccups.

I’m frustrated and just want to be able to play the game as intended.

2

We need some internet test data to help you troubleshoot.

Please follow the instructions outlined at the top of the forum here:

1 Like
3
4

Also getting high world ms but normal home ms. Only started today

5

Experiencing similar issues.

7

I just hit a World alittle over 6000 MS ping but my home was like 132. this has also been going on non stop and now I can not even log into one of my toons b/c she falling to her death from trying to fly from 1 point to another point and tried using the Get unstuck thingy… So I can hop on the other toons and not a problem but can’t hop on my other since she well waving @ me falling pretty much LOL! but yes Blizz this has been an on going issues for the World MS Pings.

8

Also getting random high ping and dc from instances. Game is unplayable for the last two days as I never know when I’m going to dc or lag out.

9

This is a DxDiag, but we need a WinMTR (connection test). I will also note there are issues happening with an app:

Problem signature:
P1: ROGLiveService.exe

10 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              puma7-atom -   35 |  129 |   85 |    2 |   30 |  399 |    4 |
|                            99.226.104.1 -   31 |  137 |   95 |   16 |   49 |  356 |   17 |
|                           24.156.135.41 -   35 |  129 |   85 |   13 |   41 |  116 |   62 |
|                         209.148.224.186 -   33 |  133 |   90 |   12 |   57 |  420 |   68 |
|       9015-cgw01.ym.rmgt.net.rogers.com -   36 |  125 |   80 |   14 |   45 |  151 |   14 |
|                          209.148.237.21 -   39 |  121 |   75 |   37 |   83 |  391 |   42 |
|                eqix-ix-ch1.blizzard.com -   31 |  137 |   95 |   36 |   79 |  420 |   43 |
|                   No response from host -  100 |   61 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   61 |    0 |    0 |    0 |    0 |    0 |
|        et-0-0-0-pe03-swlv10.as57976.net -   35 |  129 |   85 |   75 |  120 |  455 |   89 |
|                           137.221.105.2 -   36 |  125 |   80 |   87 |  124 |  441 |  141 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Tracing route to 137.221.105.2 over a maximum of 30 hops

  1     2 ms     1 ms     3 ms  puma7-atom [192.168.0.1]
  2    39 ms    16 ms    14 ms  99.226.104.1
  3    22 ms    16 ms    20 ms  24.156.135.41
  4    14 ms    32 ms    35 ms  209.148.224.186
  5    45 ms    26 ms    34 ms  9015-cgw01.ym.rmgt.net.rogers.com [209.148.224.181]
  6    43 ms    38 ms    42 ms  209.148.237.21
  7    65 ms    69 ms    53 ms  eqix-ix-ch1.blizzard.com [208.115.136.85]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    88 ms    89 ms   107 ms  et-0-0-0-pe03-swlv10.as57976.net [137.221.83.85]
 11    96 ms    88 ms    92 ms  137.221.105.2

Trace complete.

Tracing route to 137.221.105.2 over a maximum of 30 hops

  1     3 ms     1 ms     2 ms  puma7-atom [192.168.0.1]
  2    17 ms    27 ms    14 ms  99.226.104.1
  3     *      119 ms    26 ms  24.156.135.41
  4     *        *       19 ms  209.148.224.186
  5    24 ms    20 ms    15 ms  9015-cgw01.ym.rmgt.net.rogers.com [209.148.224.181]
  6    41 ms    50 ms    39 ms  209.148.237.21
  7    38 ms    41 ms    41 ms  eqix-ix-ch1.blizzard.com [208.115.136.85]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    97 ms    93 ms    78 ms  et-0-0-0-pe03-swlv10.as57976.net [137.221.83.85]
 11     *        *      104 ms  137.221.105.2

Trace complete.
11

Something’s up with your home network. The average ping to hardware in your home should be 0-1ms, not 30ms. Maybe you have interference if you’re wireless, maybe a cable is bad, maybe it’s the device itself. Not sure, but the ISP can probably help.

12

Ive contacted my isp, they say no issue and ive tried both wireless and ethernet no difference

13

Given this right here I’m amazed you only recently started having issues. The Puma 7 chipset suffered from high latency / dropped packets just like the Puma 6 chip it was made to replace. I know there was a lawsuit over Puma 6 it was so bad.

The only fix is to replace your modem with one that uses a different chip. Broadcom based modems work well from my experience.

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.