Battle.net Looking Glass. Help Packloss even on wired connection? [Canada - Teksavvy]

MaJJeK-1151 · May 28, 2019, 4:53am

I am getting frequent internet disconnection/interruptions and can not figure out what is going on. Does this ‘Looking Glass’ make sense to anyone?

TRACEROUTE:
traceroute to 198.48.155.250 (198.48.155.250), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  4.196 ms  4.189 ms  4.191 ms Blizzard(24.105.18.3)  11.025 ms  11.108 ms  11.125 ms
 3  137.221.105.16 (137.221.105.16)  11.075 ms  11.103 ms  11.131 ms
 4  137.221.66.22 (137.221.66.22)  10.981 ms  10.996 ms  11.003 ms
 5  137.221.83.68 (137.221.83.68)  34.884 ms  34.917 ms  34.925 ms
 6  * * *
 7  137.221.65.1 (137.221.65.1)  32.423 ms  32.434 ms  31.852 ms
 8  137.221.65.7 (137.221.65.7)  31.833 ms  31.832 ms  31.826 ms
 9  137.221.65.116 (137.221.65.116)  31.729 ms  31.733 ms  30.893 ms
10  137.221.65.41 (137.221.65.41)  31.018 ms  32.529 ms  32.493 ms
11  137.221.73.32 (137.221.73.32)  32.225 ms  30.835 ms  30.878 ms
12  six.teksavvy. com (206.81.81.47)  34.616 ms  34.614 ms  34.619 ms
13  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  47.263 ms  47.289 ms  47.293 ms
14  104-246-174-202.cpe.teksavvy. com (104.246.174.202)  48.263 ms  48.301 ms  47.917 ms
15  dx3ai-g10.cg.shawcable. net (64.59.131.154)  50.130 ms  50.136 ms  49.587 ms


28/05/2019 04:46:33 UTC
--------------------

TRACEROUTE:
traceroute to 198.48.155.250 (198.48.155.250), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.678 ms  0.696 ms  0.704 ms Blizzard(24.105.18.3)  0.933 ms  1.085 ms  1.151 ms
 3  137.221.105.16 (137.221.105.16)  1.041 ms  1.129 ms  1.462 ms
 4  137.221.66.22 (137.221.66.22)  1.075 ms  1.086 ms  1.095 ms
 5  137.221.83.68 (137.221.83.68)  30.591 ms  30.642 ms  44.651 ms
 6  * * *
 7  137.221.65.1 (137.221.65.1)  31.706 ms  31.347 ms  31.336 ms
 8  137.221.65.7 (137.221.65.7)  31.356 ms  31.373 ms  31.378 ms
 9  137.221.65.116 (137.221.65.116)  31.176 ms  31.209 ms  30.741 ms
10  137.221.65.41 (137.221.65.41)  30.288 ms  30.220 ms  30.217 ms
11  137.221.73.32 (137.221.73.32)  33.632 ms  33.647 ms  33.648 ms
12  six.teksavvy. com (206.81.81.47)  36.344 ms  36.373 ms  36.588 ms
13  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  50.296 ms  50.315 ms  50.322 ms
14  104-246-174-202.cpe.teksavvy. com (104.246.174.202)  51.025 ms  47.934 ms  47.892 ms
15  dx3ai-g10.cg.shawcable. net (64.59.131.154)  49.638 ms  49.600 ms  49.746 ms


28/05/2019 04:46:33 UTC
--------------------

PING:
PING 198.48.155.250 (198.48.155.250) 56(84) bytes of data.

--- 198.48.155.250 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms



28/05/2019 04:46:33 UTC
--------------------

PING:
PING 198.48.155.250 (198.48.155.250) 56(84) bytes of data.

--- 198.48.155.250 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



28/05/2019 04:46:33 UTC
--------------------

MTR:
Start: Tue May 28 04:46:33 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.4   2.1   0.2  12.3   3.9 Blizzard 0.0%    10    0.7   1.6   0.6   8.3   2.3
  3.|-- 137.221.105.16                       0.0%    10    0.5   0.8   0.5   2.5   0.5
  4.|-- 137.221.66.22                        0.0%    10    0.6   0.7   0.5   0.8   0.0
  5.|-- 137.221.83.68                        0.0%    10  462.7 212.8  30.1 585.1 235.9
  6.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.65.1                         0.0%    10   29.9  54.0  29.9 156.0  45.4
  8.|-- 137.221.65.7                         0.0%    10   30.0  33.9  30.0  56.4   8.6
  9.|-- 137.221.65.116                       0.0%    10   30.1  32.5  30.1  52.8   7.1
 10.|-- 137.221.65.41                        0.0%    10   30.2  30.2  29.9  30.4   0.0
 11.|-- 137.221.73.32                        0.0%    10   30.4  38.1  30.2  90.0  19.0
 12.|-- six.teksavvy. com                     0.0%    10   33.2  34.1  33.1  41.5   2.6
 13.|-- ae2-0-bdr01-cgr.teksavvy. com         0.0%    10   47.1  47.4  47.0  50.1   0.9
 14.|-- 104-246-174-202.cpe.teksavvy. com     0.0%    10   47.9  48.0  47.9  48.2   0.0
 15.|-- dx3ai-g10.cg.shawcable. net           0.0%    10   49.6  49.7  49.6  50.0   0.0
 16.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0


28/05/2019 04:46:33 UTC
--------------------

MTR:
Start: Tue May 28 04:46:33 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.7   0.4   0.2   0.7   0.0 Blizzard 0.0%    10    0.7   7.5   0.6  36.5  14.3
  3.|-- 137.221.105.16                       0.0%    10    0.5   0.7   0.5   0.9   0.0
  4.|-- 137.221.66.22                        0.0%    10    0.7   0.7   0.5   0.8   0.0
  5.|-- 137.221.83.68                        0.0%    10  415.2 213.7  30.1 562.6 240.4
  6.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.65.1                         0.0%    10   33.4  71.1  30.1 291.1  82.6
  8.|-- 137.221.65.7                         0.0%    10   30.2  30.2  30.0  30.3   0.0
  9.|-- 137.221.65.116                       0.0%    10   30.3  33.1  30.0  59.1   9.1
 10.|-- 137.221.65.41                        0.0%    10   32.6  30.4  30.0  32.6   0.7
 11.|-- 137.221.73.32                        0.0%    10   30.3  31.7  30.2  42.6   3.8
 12.|-- six.teksavvy. com                     0.0%    10   33.2  33.3  33.2  33.4   0.0
 13.|-- ae2-0-bdr01-cgr.teksavvy. com         0.0%    10   47.0  47.7  47.0  53.4   1.9
 14.|-- 104-246-174-202.cpe.teksavvy. com     0.0%    10   48.4  47.9  47.8  48.4   0.0
 15.|-- dx3ai-g10.cg.shawcable. net           0.0%    10   49.6  49.7  49.6  49.8   0.0
 16.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0


28/05/2019 04:46:33 UTC
--------------------

Nicole-1893 · May 29, 2019, 12:03am

Can you provide a WinMTR instead?

WinMTR instructions (click to expand/collapse)

Follow the support documentation for WinMTR. If you’re unable to get into a game for the IP address, then use an IP from the table provided on that page that matches your region. Run the test until you encounter the issue again, or for at least 10 minutes.

Share your results in a reply:

Click the “Copy Text to clipboard” button after you’ve finished the test per the instructions.
Paste the text in a reply, then highlight the pasted text and click </> on the post editor.
Break any links by adding a space before .com, .net, etc.

Zenlaka · June 2, 2019, 9:24pm

A post was split to a new topic: Overwatch latency [WideOpenWest]

Charvel-1889 · June 2, 2019, 9:05pm

same thing happening here help please

MaJJeK-1151 · June 2, 2019, 9:05pm

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            192.168.50.1 -    0 |  702 |  702 |    0 |    0 |    3 |    0 |
|                             96.51.128.1 -    0 |  701 |  701 |    8 |   31 | 2534 |    9 |
|          rc3so-be109-1.cg.shawcable.net -    0 |  702 |  702 |   20 |   41 |  334 |   20 |
|      xe-1-0-1-87-bdr01-cgr.teksavvy. com -    0 |  702 |  702 |    6 |   27 |  337 |    9 |
|                ae4.cr1-cgy1.ip4.gtt. net -    0 |  702 |  702 |    8 |   30 |  338 |   10 |
|           xe-0-3-0.cr7-sea2.ip4.gtt. net -   10 |  515 |  468 |   61 |   84 |  367 |   63 |
|                             ip4.gtt. net -    0 |  702 |  702 |   24 |   49 |  352 |   25 |
|              ae1-br01-eqse2.as57976. net -    0 |  702 |  702 |   51 |   83 | 1112 |   52 |
|       xe-0-0-0-1-br01-eqsv5.as57976. net -    0 |  702 |  702 |   49 |   82 | 1198 |   53 |
|        et-0-0-29-br02-eqsv5.as57976. net -    0 |  702 |  702 |   44 |   76 | 1304 |   49 |
|       xe-0-0-1-1-br02-eqla1.as57976. net -    0 |  702 |  702 |   51 |   86 |  881 |   56 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  141 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Zenlaka · June 2, 2019, 9:23pm

It looks like you are getting massive latency spikes here between the modem and ISP. This may be causing the disconnects and I’d suggest contacting your ISP so they can get this further investigated.

MeowjinBoo-1246 · June 4, 2019, 3:52am

Yikes, one of your techs redirected me here.

I sent this to teksavvy and they replied back with “BUT YOUR INTERNET SPEEDS ARE HIGHER THAN YOUR PAYING FOR SO THATS GOOD!”

MaJJeK-1151 · June 7, 2019, 1:34am

I too am with teksavvy. So I am wondering if they are part of the issue. I live in Calgary, AB, CA.

Edit: Interesting forum - https://www.reddit.com/r/techsupport/comments/8cpysy/non_intel_puma_6_chipset_modems_help/

Drakuloth · June 7, 2019, 10:52pm

MajjeK,

Question, did you catch a disconnection when you ran that winMTR? If not, can you create another which catches a disconnection?

If it’s a Puma issue, the winMTR may not see the problem, but there’s no clear sign of packet loss in your last test which is odd. What make/model of modem/router are you using?

MaJJeK-1151 · June 15, 2019, 6:15pm

Drakuloth,

In my post above I did catch a disconnection.

I have since acquired a new modem which does not have the puma 6 chip set. So that crosses that off the list of possible reasons.

The modem I am using is a TC4400 V2 AM
The Router I am using is a Asus RT-AC86U

I recently ran the blizzard looking glass while directly connected to my modem. It shows a weird ping spike on the 6th hop. Also interesting to note the 100 packet loss with the ping function.

TRACEROUTE:
traceroute to 198.48.149.110 (198.48.149.110), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.365 ms  0.352 ms  0.399 ms
 2  24.105.18.131 (24.105.18.131)  1.032 ms  1.031 ms  1.031 ms
 3  137.221.105.16 (137.221.105.16)  1.006 ms  1.016 ms  1.016 ms
 4  137.221.66.18 (137.221.66.18)  0.769 ms  0.776 ms  0.778 ms
 5  137.221.83.66 (137.221.83.66)  25.027 ms  25.065 ms  25.071 ms
 6  137.221.65.68 (137.221.65.68)  1888.005 ms  1885.898 ms  1885.899 ms
 7  137.221.68.32 (137.221.68.32)  10.517 ms  10.545 ms  10.545 ms
 8  213.248.78.166 (213.248.78.166)  5.910 ms  5.919 ms  5.904 ms
 9  sjo-b21-link.telia. net (62.115.116.40)  12.279 ms  12.353 ms  12.099 ms
10  213.248.66.93 (213.248.66.93)  34.008 ms  38.366 ms  38.366 ms
11  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  55.108 ms  50.956 ms  50.948 ms
12  76-10-191-142.dsl.teksavvy. com (76.10.191.142)  46.793 ms  46.851 ms  46.906 ms
13  dx3ai-g10.cg.shawcable. net (64.59.131.154)  48.566 ms  48.739 ms  48.826 ms
14  * * *
15  * * *


15/06/2019 17:32:27 UTC
--------------------

TRACEROUTE:
traceroute to 198.48.149.110 (198.48.149.110), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.326 ms  0.341 ms  0.360 ms
 2  24.105.18.131 (24.105.18.131)  1.208 ms  1.282 ms  1.313 ms
 3  137.221.105.16 (137.221.105.16)  1.232 ms  1.248 ms  1.282 ms
 4  137.221.66.18 (137.221.66.18)  0.620 ms  0.777 ms  0.800 ms
 5  137.221.83.66 (137.221.83.66)  74.651 ms  74.665 ms  74.678 ms
 6  137.221.65.68 (137.221.65.68)  1943.715 ms  1941.111 ms  1941.088 ms
 7  137.221.68.32 (137.221.68.32)  5.543 ms  5.574 ms  5.695 ms
 8  213.248.78.166 (213.248.78.166)  5.812 ms  5.674 ms  5.807 ms
 9  sjo-b21-link.telia. net (62.115.116.40)  12.387 ms  12.568 ms  12.708 ms
10  213.248.66.93 (213.248.66.93)  33.927 ms  33.993 ms  34.144 ms
11  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  45.804 ms  45.742 ms  45.742 ms
12  76-10-191-142.dsl.teksavvy. com (76.10.191.142)  46.789 ms  46.715 ms  46.974 ms
13  dx3ai-g10.cg.shawcable. net (64.59.131.154)  48.520 ms  48.654 ms  48.518 ms
14  * * *
15  * * *


15/06/2019 17:32:27 UTC
--------------------

PING:
PING 198.48.149.110 (198.48.149.110) 56(84) bytes of data.

--- 198.48.149.110 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3003ms



15/06/2019 17:32:27 UTC
--------------------

PING:
PING 198.48.149.110 (198.48.149.110) 56(84) bytes of data.

--- 198.48.149.110 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3009ms



15/06/2019 17:32:27 UTC
--------------------

MTR:
Start: Sat Jun 15 17:32:27 2019 Blizzard  1.|-- Blizzard                   0.0%    10    0.4   0.5   0.3   1.4   0.0
  2.|-- 24.105.18.131                   0.0%    10    9.5   1.8   0.5   9.5   2.8
  3.|-- 137.221.105.16                  0.0%    10    0.7   0.7   0.5   0.9   0.0
  4.|-- 137.221.66.18                   0.0%    10    0.6   0.7   0.5   1.3   0.0
  5.|-- 137.221.83.66                   0.0%    10   49.3  10.7   3.1  49.3  13.7
  6.|-- 137.221.65.68                   0.0%    10   51.6 242.1   5.7 1757. 554.6
  7.|-- 137.221.68.32                   0.0%    10    5.7   5.7   5.5   5.9   0.0
  8.|-- 213.248.78.166                  0.0%    10    5.9   5.9   5.8   6.1   0.0
  9.|-- sjo-b21-link.telia. net          0.0%    10   12.4  12.5  12.3  13.7   0.3
 10.|-- 213.248.66.93                   0.0%    10   34.0  34.1  33.9  34.5   0.0
 11.|-- ae2-0-bdr01-cgr.teksavvy. com    0.0%    10   45.9  46.0  45.8  46.4   0.0
 12.|-- 76-10-191-142.dsl.teksavvy. com  0.0%    10   47.0  47.2  46.8  48.0   0.0
 13.|-- dx3ai-g10.cg.shawcable. net      0.0%    10   48.6  48.9  48.5  50.9   0.5
 14.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0


15/06/2019 17:32:27 UTC
--------------------

MTR:
Start: Sat Jun 15 17:32:27 2019 Blizzard  1.|-- Blizzard                   0.0%    10    0.2   0.3   0.2   0.5   0.0
  2.|-- 24.105.18.131                   0.0%    10    0.6   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.16                  0.0%    10    0.5   0.6   0.5   0.9   0.0
  4.|-- 137.221.66.18                   0.0%    10    0.5   0.6   0.5   0.8   0.0
  5.|-- 137.221.83.66                   0.0%    10  141.1  18.0   1.7 141.1  43.3
  6.|-- 137.221.65.68                   0.0%    10  141.3 262.4   5.5 1657. 532.6
  7.|-- 137.221.68.32                   0.0%    10    5.5   8.7   5.5  36.2   9.6
  8.|-- 213.248.78.166                  0.0%    10    5.9   6.0   5.8   7.0   0.0
  9.|-- sjo-b21-link.telia. net          0.0%    10   12.4  12.4  12.2  13.4   0.0
 10.|-- 213.248.66.93                   0.0%    10   34.0  34.1  33.9  34.2   0.0
 11.|-- ae2-0-bdr01-cgr.teksavvy. com    0.0%    10   46.0  46.0  45.9  46.1   0.0
 12.|-- 76-10-191-142.dsl.teksavvy. com  0.0%    10   47.0  47.1  46.9  47.9   0.0
 13.|-- dx3ai-g10.cg.shawcable. net      0.0%    10   48.6  48.7  48.5  48.9   0.0
 14.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0


15/06/2019 17:32:27 UTC
--------------------

















When connected back to the router I get slightly different results:

TRACEROUTE:
traceroute to 198.48.155.250 (198.48.155.250), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.463 ms  0.447 ms  0.447 ms
 2  24.105.18.3 (24.105.18.3)  34.957 ms  34.978 ms  34.983 ms
 3  137.221.105.16 (137.221.105.16)  1.429 ms  1.431 ms  1.430 ms
 4  137.221.66.22 (137.221.66.22)  1.349 ms  1.365 ms  1.366 ms
 5  137.221.83.68 (137.221.83.68)  5.372 ms  5.385 ms  5.386 ms
 6  137.221.65.68 (137.221.65.68)  7.250 ms  7.241 ms  7.274 ms
 7  137.221.68.32 (137.221.68.32)  15.500 ms  15.505 ms  15.504 ms
 8  213.248.78.166 (213.248.78.166)  7.449 ms  7.462 ms  7.463 ms
 9  sjo-b21-link.telia. net (62.115.116.40)  13.541 ms  16.169 ms  16.155 ms
10  sea-b2-link.telia .net (62.115.118.168)  30.689 ms  30.697 ms  30.532 ms
11  213.248.66.93 (213.248.66.93)  33.873 ms  33.913 ms  33.900 ms
12  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  51.723 ms  52.040 ms  50.125 ms
13  104-246-174-202.cpe.teksavvy. com (104.246.174.202)  50.134 ms  50.140 ms  50.388 ms
14  dx3ai-g10.cg.shawcable. net (64.59.131.154)  50.318 ms  51.211 ms  51.288 ms
15  198-48-155-250.cpe.pppoe. ca (198.48.155.250)  56.215 ms  55.692 ms  55.671 ms


15/06/2019 18:13:53 UTC
--------------------

TRACEROUTE:
traceroute to 198.48.155.250 (198.48.155.250), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.290 ms  3.425 ms  3.453 ms
 2  24.105.18.3 (24.105.18.3)  29.259 ms  29.752 ms  29.784 ms
 3  137.221.105.16 (137.221.105.16)  3.503 ms  3.528 ms  3.592 ms
 4  137.221.66.22 (137.221.66.22)  3.531 ms  3.536 ms  3.557 ms
 5  137.221.83.68 (137.221.83.68)  3.558 ms  3.576 ms  3.577 ms
 6  137.221.65.68 (137.221.65.68)  7.647 ms  5.912 ms  5.940 ms
 7  137.221.68.32 (137.221.68.32)  5.587 ms  5.643 ms  5.658 ms
 8  213.248.78.166 (213.248.78.166)  5.905 ms  6.004 ms  5.908 ms
 9  sjo-b21-link.telia. net (62.115.116.40)  12.043 ms  12.051 ms  12.411 ms
10  sea-b2-link.telia. net (62.115.118.168)  30.379 ms  30.425 ms  30.645 ms
11  213.248.66.93 (213.248.66.93)  34.032 ms  34.035 ms  33.934 ms
12  ae2-0-bdr01-cgr.teksavvy. com (206.248.155.180)  47.707 ms  47.772 ms  47.794 ms
13  104-246-174-202.cpe.teksavvy. com (104.246.174.202)  48.633 ms  48.710 ms  48.719 ms
14  dx3ai-g10.cg.shawcable. net (64.59.131.154)  50.337 ms  50.514 ms  50.534 ms
15  198-48-155-250.cpe.pppoe. ca (198.48.155.250)  55.715 ms  59.117 ms  57.186 ms


15/06/2019 18:13:53 UTC
--------------------

PING:
PING 198.48.155.250 (198.48.155.250) 56(84) bytes of data.
64 bytes from 198.48.155.250: icmp_seq=1 ttl=48 time=54.8 ms
64 bytes from 198.48.155.250: icmp_seq=2 ttl=48 time=59.4 ms
64 bytes from 198.48.155.250: icmp_seq=3 ttl=48 time=58.1 ms
64 bytes from 198.48.155.250: icmp_seq=4 ttl=48 time=55.0 ms

--- 198.48.155.250 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 54.881/56.904/59.488/1.974 ms


15/06/2019 18:13:53 UTC
--------------------

PING:
PING 198.48.155.250 (198.48.155.250) 56(84) bytes of data.
64 bytes from 198.48.155.250: icmp_seq=1 ttl=48 time=66.3 ms
64 bytes from 198.48.155.250: icmp_seq=2 ttl=48 time=57.0 ms
64 bytes from 198.48.155.250: icmp_seq=3 ttl=48 time=58.7 ms
64 bytes from 198.48.155.250: icmp_seq=4 ttl=48 time=56.7 ms

--- 198.48.155.250 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 56.772/59.729/66.396/3.926 ms


15/06/2019 18:13:53 UTC
--------------------

MTR:
Start: Sat Jun 15 18:13:53 2019 Blizzard  1.|-- Blizzard                      0.0%    10    0.3   0.4   0.3   0.6   0.0
  2.|-- 24.105.18.3                       0.0%    10    3.9   0.9   0.5   3.9   1.0
  3.|-- 137.221.105.16                    0.0%    10    0.8   0.9   0.5   2.8   0.5
  4.|-- 137.221.66.22                     0.0%    10    0.7   0.7   0.5   0.9   0.0
  5.|-- 137.221.83.68                     0.0%    10    7.5   4.5   1.3   7.9   2.4
  6.|-- 137.221.65.68                     0.0%    10    5.7   5.8   5.6   6.0   0.0
  7.|-- 137.221.68.32                     0.0%    10    5.7   5.9   5.5   8.4   0.8
  8.|-- 213.248.78.166                    0.0%    10    5.7   5.8   5.7   5.9   0.0
  9.|-- sjo-b21-link.telia. net            0.0%    10   12.4  12.9  12.0  19.3   2.1
 10.|-- sea-b2-link.telia. net             0.0%    10   30.8  31.3  30.4  33.7   0.9
 11.|-- 213.248.66.93                     0.0%    10   34.0  34.1  33.9  35.9   0.3
 12.|-- ae2-0-bdr01-cgr.teksavvy. com      0.0%    10   47.8  48.0  47.7  50.6   0.7
 13.|-- 104-246-174-202.cpe.teksavvy. com  0.0%    10   48.5  48.8  48.4  49.2   0.0
 14.|-- dx3ai-g10.cg.shawcable. net        0.0%    10   50.5  50.4  50.3  50.6   0.0
 15.|-- 198-48-155-250.cpe.pppoe. ca       0.0%    10   57.5  57.1  54.9  58.9   1.2


15/06/2019 18:13:53 UTC
--------------------

MTR:
Start: Sat Jun 15 18:13:53 2019 Blizzard  1.|-- Blizzard                      0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.3                       0.0%    10    0.5   1.8   0.5   5.9   1.9
  3.|-- 137.221.105.16                    0.0%    10    0.6   0.7   0.5   0.9   0.0
  4.|-- 137.221.66.22                     0.0%    10    0.8   0.8   0.5   2.0   0.3
  5.|-- 137.221.83.68                     0.0%    10    6.2   4.6   0.9   8.8   2.9
  6.|-- 137.221.65.68                     0.0%    10    5.8   8.7   5.6  27.7   6.9
  7.|-- 137.221.68.32                     0.0%    10    5.7   6.2   5.5  10.7   1.5
  8.|-- 213.248.78.166                    0.0%    10    6.0   5.9   5.7   7.0   0.0
  9.|-- sjo-b21-link.telia. net            0.0%    10   12.4  12.3  12.0  12.6   0.0
 10.|-- sea-b2-link.telia. net             0.0%    10   30.7  31.1  30.5  33.2   0.6
 11.|-- 213.248.66.93                     0.0%    10   33.9  34.1  33.9  35.2   0.3
 12.|-- ae2-0-bdr01-cgr.teksavvy. com      0.0%    10   48.4  47.9  47.6  48.4   0.0
 13.|-- 104-246-174-202.cpe.teksavvy. com  0.0%    10   48.7  48.7  48.5  48.9   0.0
 14.|-- dx3ai-g10.cg.shawcable. net        0.0%    10   50.5  50.4  50.3  50.6   0.0
 15.|-- 198-48-155-250.cpe.pppoe. ca       0.0%    10   56.3  57.3  55.0  58.9   0.9


15/06/2019 18:13:53 UTC
--------------------

Drakuloth · June 15, 2019, 9:10pm

Since you have a separate modem and router, can you try bypassing the router and retrying? It basically looks like there MAY have been a packet drop right around there during your WinMTR, but the test has a couple quirks that make it hard to confirm.

Your looking glass tests are all fine, I wouldn’t worry about them for this issue. If you truly had 100% packet loss, you wouldn’t be able to connect at all. What you’re seeing is just an ISP between you and us blocking test packets, and that’s the readout we get when that’s the case.

MaJJeK-1151 · June 15, 2019, 9:13pm

Drakuloth

The issue persists if I by pass the router and connect straight to the modem. Or are you asking to do another WinMTR capture of the error while connect straight to the modem?

Would it be possible to contact you via telephone?

Drakuloth · June 15, 2019, 9:18pm

MaJJeK,

You wouldn’t be able to contact me directly, but we do have a support team which can look over it with you if you prefer live one on one help.

We might try to catch a problem with winMTR while connected direct to modem before submitting the ticket - that’ll make sure that we have information that’s as up to date as possible.

MaJJeK-1151 · June 15, 2019, 9:22pm

Would you like me to get a WinMTR of the issue while connected directly to the modem? Your last message wasnt quite clear on that

edit:

Looks like something similar to my posts. With the ping spike on ‘137.221.65.68’

Drakuloth · June 15, 2019, 10:48pm

Regarding running the winMTR while connected to the modem: that would be useful if you can do that, yes. As for that spike, it doesn’t persist all throughout the test. I’m not super worried about it, it’s probably that hop actually ignoring the packets and the test getting the wrong information in response.

MorningStar-21810 · June 18, 2019, 2:00am

hello MaJJeK i have the same problem as you what is weird using a simple ip lookup (where it is based is not 100% correct but usually close) it seems like the ip is located in the netherlands (what is funny i have the same issue you have but only in competitive play) are you sure you are connected to the right server or something cause ams1 is i think EU servers