Poor network performance with new Los Angeles ISP (Starry Internet)

Hi, I live in downtown Los Angeles and I recently switched to a new ISP (Starry Internet). Unfortunately, I’ve noticed that since switching, my network performance in Overwatch seems much worse. The in-game latency never gets lower than 110 ms, and using the Ctrl+Shift+‘N’ diagnostics shows that the game is placing me on the Chicago server instead of the Los Angeles one.

I thought this must be wrong, but when I did a Trace Route, it confirmed that the Chicago server was technically better, but only because the connection to the LA server was going through France(?):

 Tracing route to 24.105.30.129 (LA Server) over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.99.1
  2    13 ms    10 ms    10 ms  8.3.88.1
  3    78 ms    78 ms    78 ms  rt01-te-0-2-2.ashburn.va.starry-inc.net [205.201.16.130]
  4    72 ms    77 ms    78 ms  equinix-iad.rt01.ashburn.va.starry-inc.net [206.126.238.35]
  5    77 ms    78 ms    78 ms  eqix-dc2.blizzard.com [206.126.237.174]
  6   137 ms   138 ms   135 ms  ae1-br01-eqdc2.as57976.net [137.221.72.33]
  7   133 ms   137 ms   135 ms  et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
  8   137 ms   138 ms   137 ms  137.221.65.132
  9   471 ms   657 ms   659 ms  et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
 10   137 ms   137 ms   138 ms  be1-pe01-eqla1.as57976.net [137.221.68.67]
 11   137 ms   137 ms   138 ms  lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
 12   135 ms   134 ms   137 ms  24.105.30.129

Trace complete.

C:\WINDOWS\system32>tracert 24.105.62.129

Tracing route to 24.105.62.129 (Chicago Server) over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.99.1
  2     8 ms     9 ms    10 ms  8.3.88.1
  3    78 ms    77 ms    78 ms  rt01-te-0-2-2.ashburn.va.starry-inc.net [205.201.16.130]
  4    72 ms    73 ms    77 ms  equinix-iad.rt01.ashburn.va.starry-inc.net [206.126.238.35]
  5    72 ms    76 ms    86 ms  eqix-dc2.blizzard.com [206.126.237.174]
  6    92 ms    93 ms    93 ms  ae1-br01-eqdc2.as57976.net [137.221.72.33]
  7    80 ms    86 ms    82 ms  et-0-0-2-br01-eqch2.as57976.net [137.221.65.13]
  8    93 ms    93 ms    94 ms  be1-pe01-eqch2.as57976.net [137.221.69.67]
  9    93 ms    93 ms    93 ms  24.105.62.129

Trace complete.

I also used the Looking Glass site and got back these results:

TRACEROUTE:
traceroute to 8.3.92.239 (8.3.92.239), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  3.678 ms  3.671 ms  3.675 ms Blizzard(24.105.18.3)  3.678 ms  3.683 ms  3.687 ms
 3  137.221.105.12 (137.221.105.12)  3.515 ms  3.553 ms  3.598 ms
 4  137.221.66.16 (137.221.66.16)  3.556 ms  3.564 ms  3.569 ms
 5  137.221.83.66 (137.221.83.66)  72.619 ms  72.647 ms  72.657 ms
 6  137.221.65.133 (137.221.65.133)  57.522 ms  57.062 ms  57.110 ms
 7  137.221.65.12 (137.221.65.12)  57.071 ms  57.075 ms  57.090 ms
 8  137.221.72.32 (137.221.72.32)  56.245 ms  55.568 ms  55.666 ms
 9  equinix-iad.rt01.ashburn.va.starry-inc.net (206.126.238.35)  55.539 ms  55.526 ms  55.485 ms
10  * * *
11  8.3.88.1 (8.3.88.1)  121.548 ms  121.561 ms  121.569 ms
12  * * *
13  * * *
14  * * *
15  * * *


20/03/2019 19:01:25 UTC
--------------------

TRACEROUTE:
traceroute to 8.3.92.239 (8.3.92.239), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  11.924 ms  11.928 ms  11.934 ms Blizzard(24.105.18.3)  11.941 ms  11.950 ms  11.943 ms
 3  137.221.105.12 (137.221.105.12)  11.004 ms  11.047 ms  11.055 ms
 4  137.221.66.16 (137.221.66.16)  11.012 ms  11.021 ms  11.051 ms
 5  137.221.83.66 (137.221.83.66)  64.290 ms  64.303 ms  64.313 ms
 6  137.221.65.133 (137.221.65.133)  64.073 ms  55.664 ms  57.166 ms
 7  137.221.65.12 (137.221.65.12)  57.384 ms  57.406 ms  57.411 ms
 8  137.221.72.32 (137.221.72.32)  56.803 ms  55.729 ms  55.850 ms
 9  equinix-iad.rt01.ashburn.va.starry-inc.net (206.126.238.35)  55.521 ms  55.888 ms  55.903 ms
10  * * *
11  8.3.88.1 (8.3.88.1)  123.060 ms  122.439 ms  121.566 ms
12  * * *
13  * * *
14  * * *
15  * * *


20/03/2019 19:01:25 UTC
--------------------

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

--- 8.3.92.239 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2997ms



20/03/2019 19:01:25 UTC
--------------------

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

--- 8.3.92.239 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



20/03/2019 19:01:25 UTC
--------------------

MTR:
Start: Wed Mar 20 19:01:25 2019 Blizzard  1.|-- Blizzard                                0.0%    10    0.4   0.4   0.3   0.6   0.0 Blizzard        0.0%    10    0.8   0.7   0.6   1.1   0.0
  3.|-- 137.221.105.12                              0.0%    10    0.7   1.0   0.5   3.7   0.8
  4.|-- 137.221.66.16                               0.0%    10    0.7   0.8   0.5   1.6   0.0
  5.|-- 137.221.83.66                               0.0%    10   56.1  56.1  55.9  56.6   0.0
  6.|-- 137.221.65.133                              0.0%    10   56.0  58.1  55.8  76.9   6.6
  7.|-- 137.221.65.12                               0.0%    10   56.1  56.0  55.7  56.1   0.0
  8.|-- 137.221.72.32                               0.0%    10   55.6  55.8  55.6  56.2   0.0
  9.|-- equinix-iad.rt01.ashburn.va.starry-inc.net  0.0%    10   55.4  55.5  55.4  55.7   0.0
 10.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- 8.3.88.1                                    0.0%    10  121.7 121.8 121.5 121.9   0.0
 12.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0


20/03/2019 19:01:25 UTC
--------------------

MTR:
Start: Wed Mar 20 19:01:25 2019 Blizzard  1.|-- Blizzard                                0.0%    10    0.3   0.4   0.3   0.5   0.0 Blizzard        0.0%    10    0.8   0.9   0.6   1.7   0.0
  3.|-- 137.221.105.12                              0.0%    10    0.8   1.0   0.6   3.7   0.7
  4.|-- 137.221.66.16                               0.0%    10    0.8   0.8   0.5   1.6   0.0
  5.|-- 137.221.83.66                               0.0%    10   56.1  56.1  55.9  56.5   0.0
  6.|-- 137.221.65.133                              0.0%    10   56.0  58.1  55.9  77.2   6.7
  7.|-- 137.221.65.12                               0.0%    10   56.1  56.0  55.8  56.2   0.0
  8.|-- 137.221.72.32                               0.0%    10   55.7  55.8  55.7  56.2   0.0
  9.|-- equinix-iad.rt01.ashburn.va.starry-inc.net  0.0%    10   55.5  55.6  55.4  55.7   0.0
 10.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- 8.3.88.1                                    0.0%    10  121.8 121.8 121.7 121.9   0.0
 12.|-- ???                                        100.0    10    0.0   0.0   0.0   0.0   0.0


20/03/2019 19:01:25 UTC
--------------------

I have tried all of the network troubleshooting steps outlined in the ‘common issues’ threads, and nothing has made a difference in the issue. I was just hoping somebody could confirm whether this is an issue with Blizzard’s routing, or if this is something I need to contact my ISP about.

Thanks!

In your traceroute your ping rate really spikes up more than usual on the third hub. This hub is likely controlled by your ISP.

Ok, thanks, I’ll send them a message and see why they’re routing everything through Boston.

Hey MonkyBusiness, long time no talk! We had a cross-connect issue when we first launched in LA that we fixed when you emailed us back in March. As always, feel free to reach out to us at support@starry.com with any issues!

1 Like