[Mar 11]Higher than normal latency on MegaCable/Mexico

Technical Support
1

I usually play with 40ms ping to Lax1 server, but since almost a week from now I’ve been playing with 140-160ms ping. I did the WinMTR test but I don’t understand the results, can anyone help? Thank you in advance.

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 0 | 102 | 102 | 0 | 1 | 13 | 1 |

| 10.117.64.1 - 0 | 102 | 102 | 8 | 11 | 22 | 10 |

| 10.5.4.94 - 0 | 102 | 102 | 8 | 12 | 24 | 11 |

| 10.0.81.166 - 0 | 102 | 102 | 8 | 11 | 22 | 13 |

| 10.1.81.233 - 0 | 102 | 102 | 8 | 12 | 25 | 15 |

| 10.0.81.169 - 0 | 102 | 102 | 9 | 13 | 28 | 14 |

| 10.3.2.142 - 0 | 102 | 102 | 50 | 55 | 69 | 56 |

| 10.3.0.30 - 0 | 102 | 102 | 48 | 52 | 67 | 49 |

| 10.3.0.42 - 0 | 102 | 102 | 52 | 56 | 72 | 55 |

| 10.3.0.54 - 0 | 102 | 102 | 46 | 50 | 64 | 49 |

| 10.3.5.13 - 0 | 102 | 102 | 51 | 55 | 71 | 51 |

| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 20 | 0 | 0 | 0 | 0 | 0 |

| 10.3.0.1 - 0 | 102 | 102 | 46 | 50 | 64 | 50 |

| 201-174-154-17.transtelco .net - 0 | 102 | 102 | 37 | 41 | 52 | 37 |

| 201-174-250-245.transtelco .net - 0 | 102 | 102 | 53 | 58 | 73 | 56 |

| eqix-dc2.blizzard .com - 0 | 102 | 102 | 87 | 92 | 114 | 96 |

| ae1-br01-eqdc2.as57976 .net - 0 | 102 | 102 | 118 | 129 | 423 | 119 |

| et-0-0-2-br01-eqch2.as57976 .net - 12 | 62 | 55 | 118 | 421 | 3299 | 1979 |

| 137.221.65.132 - 0 | 102 | 102 | 114 | 143 | 796 | 120 |

| et-0-0-2-br01-eqla1.as57976 .net - 0 | 102 | 102 | 103 | 108 | 141 | 108 |

| be1-pe01-eqla1.as57976 .net - 0 | 102 | 102 | 114 | 118 | 130 | 121 |

| 24.105.30.129 - 0 | 102 | 102 | 114 | 120 | 137 | 123 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

2

Hey, LaMancha! Thank you for the WinMTR test! The connection test is showing some high latency about 120-140ms by the time it reaches the US West servers. Just a few questions!

  • Are you on a different server now than LAX1? The server name will display with the Network Graph (CTRL+SHIFT+N). It should show something along the lines of ORD, SAE, etc.
  • If it is a different server, can a longer 5-10 minute test be ran to the LAX1 server 24.105.8.152? And
  • If you are still on the LAX1 server, let’s grab a 5-10 minute WinMTR test while in a Training Co-op vs AI using the IP from the network graph.
3

Thanks for you response Caterpepi. It has been connecting randomly to lax1 and ord1, I get 120-140ms ping from both servers. This problem started about a week ago, I usually connect to lax1 with 40ms ping.

Tonight it only let me connect to ord1. Did the 5-10 minute test WinMTR test to 24.105.8.152

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

|                                      WinMTR statistics                                   |

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

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

|                             192.168.0.1 -    0 |  376 |  376 |    0 |    0 |   11 |    0 |

|                             10.117.64.1 -    0 |  376 |  376 |    7 |   10 |   23 |   12 |

|                               10.5.4.94 -    0 |  376 |  376 |    8 |   11 |   25 |    8 |

|                             10.0.81.166 -    0 |  376 |  376 |    8 |   11 |   23 |   11 |

|                             10.1.81.233 -    1 |  373 |  372 |    7 |   10 |   31 |   10 |

|                             10.0.81.169 -    0 |  376 |  376 |    9 |   12 |   24 |   12 |

|                              10.3.2.142 -    0 |  376 |  376 |   51 |   55 |   67 |   55 |

|                               10.3.0.30 -    0 |  376 |  376 |   47 |   50 |   64 |   50 |

|                               10.3.0.42 -    0 |  376 |  376 |   51 |   55 |   66 |   56 |

|                               10.3.0.54 -    0 |  376 |  376 |   46 |   49 |   62 |   51 |

|                               10.3.5.13 -    0 |  376 |  376 |   51 |   54 |   68 |   55 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                                10.3.0.1 -    0 |  376 |  376 |   50 |   53 |   64 |   51 |

|           201-174-154-17.transtelco.net -    0 |  376 |  376 |   41 |   44 |   57 |   43 |

|          201-174-250-159.transtelco.net -    0 |  376 |  376 |   55 |   58 |   67 |   59 |

|                   eqix-dc2.blizzard.com -    0 |  376 |  376 |   90 |   94 |  118 |   93 |

|              ae1-br01-eqdc2.as57976.net -    0 |  376 |  376 |  106 |  111 |  148 |  112 |

|         et-0-0-2-br01-eqch2.as57976.net -    3 |  336 |  328 |    0 |  158 | 3958 |  108 |

|                          137.221.65.132 -    0 |  376 |  376 |  106 |  112 |  173 |  108 |

|         et-0-0-2-br01-eqla1.as57976.net -    0 |  375 |  375 |  109 |  136 | 2062 |  113 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   75 |    0 |    0 |    0 |    0 |    0 |

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

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
4

La Mancha,

You’re actually running into the same issue we’re investigating at this thread, even though you’re not on the same ISP as the players the thread is about right now. The peering on one of the backbone nodes you’re going through is messed up and your latency is jumping up way too high in Washington DC. We’re on it. In the mean time, if you use a mobile tether or VPN, it should let you work around it.

5

Just wanted to add on to this. I was suspecting the same issue as the routing issue from the Frontier issue since the latency slightly increases on the DC node. For some reason it looks like it’s going from Mexico, to DC, to Chicago, then back to US West.

This should hopefully be resolved now you, too. If you could try testing in a Training Co-op vs AI. If it continues, let’s grab a looking glass test..

6

Still have the same problem, I create a custom game and always connects me to Ord1 and have like 130ms ping. In the Practice range sometimes connects to Lax1 but ping is pretty similar to Ord1 (130-140ms). Did the looking glass test, hope it helps.

TRACEROUTE:
traceroute to 177.228.70.198 (177.228.70.198), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.376 ms  0.375 ms  0.393 ms Blizzard(24.105.18.3)  1.012 ms  1.014 ms  1.057 ms
 3  137.221.105.16 (137.221.105.16)  0.997 ms  1.037 ms  1.039 ms
 4  137.221.66.18 (137.221.66.18)  0.989 ms  0.992 ms  1.031 ms
 5  137.221.83.70 (137.221.83.70)  25.758 ms  25.779 ms  25.790 ms
 6  137.221.65.66 (137.221.65.66)  25.684 ms  25.641 ms  25.633 ms
 7  137.221.74.32 (137.221.74.32)  25.396 ms  25.554 ms  25.541 ms
 8  * * *
 9  201-174-250-158.transtelco.net (201.174.250.158)  72.131 ms  72.116 ms  72.088 ms
10  201-174-251-17.transtelco.net (201.174.251.17)  79.421 ms  79.453 ms  79.530 ms
11  201-174-154-30.transtelco.net (201.174.154.30)  82.839 ms  82.745 ms  82.767 ms
12  * * *
13  * * *
14  * * *
15  * * *


12/03/2019 01:07:49 UTC
--------------------

TRACEROUTE:
traceroute to 177.228.70.198 (177.228.70.198), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.712 ms  0.703 ms  0.711 ms Blizzard(24.105.18.3)  1.507 ms  1.731 ms  1.943 ms
 3  137.221.105.16 (137.221.105.16)  1.127 ms  1.132 ms  1.301 ms
 4  137.221.66.18 (137.221.66.18)  1.071 ms  1.256 ms  1.274 ms
 5  137.221.83.70 (137.221.83.70)  26.098 ms  26.105 ms  26.109 ms
 6  137.221.65.66 (137.221.65.66)  26.046 ms  25.940 ms  25.949 ms
 7  137.221.74.32 (137.221.74.32)  25.739 ms  25.754 ms  25.760 ms
 8  * * *
 9  201-174-250-158.transtelco.net (201.174.250.158)  72.460 ms  72.167 ms  72.144 ms
10  201-174-251-17.transtelco.net (201.174.251.17)  79.432 ms  79.311 ms  79.398 ms
11  201-174-154-30.transtelco.net (201.174.154.30)  82.843 ms  82.777 ms  82.675 ms
12  * * *
13  * * *
14  * * *
15  * * *


12/03/2019 01:07:49 UTC
--------------------

MTR:
Start: Tue Mar 12 01:07:49 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard 0.0%    10    0.5   0.8   0.5   2.7   0.5
  3.|-- 137.221.105.16                       0.0%    10    0.5   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.18                        0.0%    10    2.7   1.1   0.6   3.0   0.9
  5.|-- 137.221.83.70                        0.0%    10   25.6  27.5  25.5  44.2   5.9
  6.|-- 137.221.65.66                        0.0%    10   25.7  30.3  25.5  72.5  14.8
  7.|-- 137.221.74.32                        0.0%    10   25.4  27.4  25.3  36.3   3.9
  8.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- 201-174-250-158.transtelco.net       0.0%    10   72.3  72.2  72.1  72.4   0.0
 10.|-- 201-174-251-17.transtelco.net        0.0%    10   79.5  79.4  79.4  79.5   0.0
 11.|-- 201-174-154-30.transtelco.net        0.0%    10   82.8  82.9  82.7  83.0   0.0
 12.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0


12/03/2019 01:07:49 UTC
--------------------

MTR:
Start: Tue Mar 12 01:07:49 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard 0.0%    10    0.6   1.7   0.5  10.5   3.0
  3.|-- 137.221.105.16                       0.0%    10    0.7   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.18                        0.0%    10    0.5   0.7   0.5   0.8   0.0
  5.|-- 137.221.83.70                        0.0%    10   25.6  25.8  25.6  26.7   0.0
  6.|-- 137.221.65.66                        0.0%    10   25.5  37.9  25.5 143.9  37.2
  7.|-- 137.221.74.32                        0.0%    10   25.3  28.3  25.3  40.4   6.0
  8.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- 201-174-250-158.transtelco.net       0.0%    10   72.1  72.2  72.1  72.3   0.0
 10.|-- 201-174-251-17.transtelco.net        0.0%    10   79.4  80.1  79.3  86.3   2.1
 11.|-- 201-174-154-30.transtelco.net        0.0%    10   83.0  83.0  82.9  83.0   0.0
 12.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0


12/03/2019 01:07:49 UTC
--------------------
7

Thanks, LaMancha! It looks like there may be a similar concern with the peering nodes that occurred with Frontier or there is a routing issue that may be outside of what we can control.

We’re starting to gather information to see where the problem starts. We have a thread on our spanish forums to get some more visibility. There has been a 30-40ms increase for those on the Megacable ISP since March 6th.

For the moment, it’s recommended to contact the ISP with this information. If you’re open to doing this on your own a VPN or a different network can be used for the time being. It’s not something we can assist with, but it may help lower the latency for the time being.

I went ahead and edited the title, in case we can get more traction on this thread :slight_smile: For those on the same ISP or region experiencing this issue, please post your WinMTR and Looking Glass results.

1 Like
8

Thanks a lot for your help! I’ll contact my ISP. :+1:

1 Like