Issues Loading into Heroics

Support Technical Support
43

Please note, this is not just from Australia ISP. I am in Malaysia and having the same exact issue. Attached is the tracerout… seems that US CENTRAL server can’t even reach. Please fix this.

------------------

Tracing route to 137.221.105.2 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     2 ms     2 ms     1 ms  202.187.48.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     3 ms     3 ms     3 ms  223.28.43.70
  6    43 ms    43 ms    43 ms  203.208.131.161
  7   195 ms   195 ms   196 ms  203.208.172.154
  8   196 ms   196 ms   195 ms  203.208.171.117
  9   186 ms   186 ms   186 ms  las-b21-link.telia.net [213.248.83.124]
 10   181 ms   181 ms   186 ms  blizzard-ic-348621-las-b21.c.telia.net [62.115.178.201]
 11   199 ms   210 ms   226 ms  ae1-br01-eqla1.as57976.net [137.221.68.33]
 12     *        *        *     Request timed out.
 13   196 ms   196 ms   196 ms  et-0-0-0-pe04-swlv10.as57976.net [137.221.83.87]
 14   192 ms   191 ms   192 ms  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
 15   191 ms   191 ms   191 ms  137.221.105.2

Trace complete.

-----

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     2 ms     2 ms     2 ms  202.187.48.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    38 ms     3 ms     3 ms  223.28.43.70
  6    43 ms    43 ms    43 ms  203.208.131.161
  7    48 ms    48 ms    49 ms  203.208.158.186
  8    41 ms    41 ms    41 ms  203.208.158.18
  9   193 ms   193 ms   193 ms  203.208.172.146
 10   195 ms   194 ms   194 ms  203.208.171.118
 11     *        *        *     Request timed out.
 12   194 ms   189 ms   189 ms  ae14.cs1.lax112.us.eth.zayo.com [64.125.27.40]
 13   190 ms   192 ms   187 ms  ae2.cs1.sjc2.us.eth.zayo.com [64.125.28.144]
 14   202 ms   193 ms   193 ms  ae3.cs1.sea1.us.eth.zayo.com [64.125.29.43]
 15   193 ms   193 ms   193 ms  ae27.mpr1.sea1.us.zip.zayo.com [64.125.29.1]
 16   212 ms   212 ms   212 ms  six.blizzardonline.net [206.81.81.122]
 17   246 ms   246 ms   261 ms  ae1-br02-eqse2.as57976.net [137.221.73.35]
 18     *        *        *     Request timed out.
 19   241 ms   241 ms   241 ms  et-0-0-1-pe04-eqch2.as57976.net [137.221.69.79]
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.
44

In the first test, the ping is good at the start but then rises to 195ms in Singtel’s network (203.208.172.154 is a Singtel IP) before jumping to North American hubs.

The same is happening in the second test in the Singtel network, and continues to get worse in the Zayo hubs after Singtel. Zayo is likely a peering partner that Singtel uses.

Unfortunately, both tests are showing major issues before the connection hops to North American hubs or servers. Perhaps the staff will have more info on this situation. In the meantime, forwarding these results to your ISP is a good step to get them started on investigating the lag.

45

18hrs on mine thinking the same … good riddance