High Ping, Poor Routing

Technical Support
1

Living West Coast but the game is connecting me to central servers with 80 ping. If i’m connected to the west coast servers my ping is around 90ish. If I use my vpn to connect to west coast my ping is 50 ish. Currently affecting Overwatch.

Date and time : anytime

My IP address : 107.190.22.8

ISP : Teksavvy (on the Shaw Communincations Network)

Connection Type : Cable

Tracert

Tracing route to 24.105.30.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms    11 ms    15 ms  24.108.64.1
  3    13 ms    14 ms    14 ms  107.190.16.129
  4    15 ms    14 ms    16 ms  xe-0-2-0-905-agg01-van2.teksavvy.com [209.161.255.205]
  5    23 ms    27 ms    18 ms  sea-b2-link.telia.net [213.248.66.92]
  6    18 ms    18 ms    19 ms  blizzard-ic-333795-sea-b2.c.telia.net [213.248.66.21]
  7    95 ms    86 ms    87 ms  ae1-br01-eqse2.as57976.net [137.221.73.33]
  8    86 ms    85 ms    85 ms  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
  9   285 ms    93 ms    86 ms  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
 10    85 ms    88 ms    86 ms  be2-pe01-eqla1.as57976.net [137.221.68.71]
 11    88 ms    92 ms    86 ms  24.105.30.129

Trace complete.

Pathping

> Tracing route to 24.105.30.129 over a maximum of 30 hops
> 
>   0  DESKTOP-186GPOD [192.168.1.2] 
>   1  192.168.1.1 
>   2  24.108.64.1 
>   3  107.190.16.129 
>   4  xe-0-2-0-905-agg01-van2.teksavvy.com [209.161.255.205] 
>   5  sea-b2-link.telia.net [213.248.66.92] 
>   6  blizzard-ic-333795-sea-b2.c.telia.net [213.248.66.21] 
>   7  ae1-br01-eqse2.as57976.net [137.221.73.33] 
>   8  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
>   9  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
>  10  be2-pe01-eqla1.as57976.net [137.221.68.71] 
>  11  24.105.30.129 
> 
> Computing statistics for 275 seconds...
>             Source to Here   This Node/Link
> Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
>   0                                           DESKTOP-186GPOD [192.168.1.2] 
>                                 0/ 100 =  0%   |
>   1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 
>                                 0/ 100 =  0%   |
>   2   25ms     0/ 100 =  0%     0/ 100 =  0%  24.108.64.1 
>                                 0/ 100 =  0%   |
>   3   27ms     0/ 100 =  0%     0/ 100 =  0%  107.190.16.129 
>                                 0/ 100 =  0%   |
>   4   29ms     0/ 100 =  0%     0/ 100 =  0%  xe-0-2-0-905-agg01-van2.teksavvy.com [209.161.255.205] 
>                                 0/ 100 =  0%   |
>   5   32ms     0/ 100 =  0%     0/ 100 =  0%  sea-b2-link.telia.net [213.248.66.92] 
>                                 0/ 100 =  0%   |
>   6   27ms     0/ 100 =  0%     0/ 100 =  0%  blizzard-ic-333795-sea-b2.c.telia.net [213.248.66.21] 
>                                 0/ 100 =  0%   |
>   7   27ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br01-eqse2.as57976.net [137.221.73.33] 
>                                 0/ 100 =  0%   |
>   8  ---     100/ 100 =100%   100/ 100 =100%  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40] 
>                                 0/ 100 =  0%   |
>   9  ---     100/ 100 =100%   100/ 100 =100%  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
>                                 0/ 100 =  0%   |
>  10  ---     100/ 100 =100%   100/ 100 =100%  be2-pe01-eqla1.as57976.net [137.221.68.71] 
>                                 0/ 100 =  0%   |
>  11   99ms     0/ 100 =  0%     0/ 100 =  0%  24.105.30.129 
> 
> Trace complete.

MTR TEST

TRACEROUTE:
traceroute to 107.190.22.8 (107.190.22.8), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.427 ms  0.430 ms  0.431 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


17/01/2019 22:48:41 UTC
--------------------

TRACEROUTE:
traceroute to 107.190.22.8 (107.190.22.8), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.228 ms  0.232 ms  0.235 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


17/01/2019 22:48:41 UTC
--------------------

MTR:
Start: Thu Jan 17 22:48:41 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.4   0.2   0.6   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


17/01/2019 22:48:41 UTC
--------------------

MTR:
Start: Thu Jan 17 22:48:41 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


17/01/2019 22:48:41 UTC
2

Oof.

So the game server connects you based on the last hop you used to reach it. If this isn’t the normal route you take to reach the servers, either Teksavvy or Telia would be at fault here. When you use the VPN, your VPN service is doing the routing for you, and you’re bypassing any input from Teksavvy and Telia, that’s why the ping is lower. Bring this to your ISP’s attention.

3

Thank you very much! Any recommendations on how I should describe the problem?

4

You’re welcome. I think if you tell them the connection quality is poor because you’re being routed differently than before, and maybe send them this test and one with the VPN, that would be enough.

5

I have the exact same issue, I had to use a VPN connected to chicago to get my ping down to 50ms, otherwise it sits around 70 or above. I’m on Shaw.