350+ ping for unknown reasons (Americas)

That the routing on their network, through Telia, is responding very slowly and causing your connection to be forwarded to game servers outside the country. You may need a Level 2 or 3 tech to assist you.

This problem may resolve on its own, but it’s not really AtlanticBB’s fault. Instead, it’s the middleman between them and Blizzard. They may be limited in the assistance they can offer (this is what sucks about broadband all over the world).

I wish you good luck, and hopefully they’ll be able to track this down quickly for you.

Alright, I’ll let you know what they say. I don’t have a VPN or know any trustworthy ones either.

Damn never heard of them either. Neither of those are my ISPs. I guess my ISP uses atlanticbb?

The first few IPs in your WinMTR are masked, so I can’t read their hostnames. Whatever your ISP’s name is, they are who you need to contact to start working on a resolution.

I live in NJ and I’m having a similar issue where it looks like when i connect to OW servers i’m being routed to a non-local server. using a vpn seems to solve the issue but I’ve never had this issue before.

Noted, thanks much Nicole. I’ll reach out to them tomm

1 Like

Define non-local. Do you mean Los Angeles?

So I called, they don’t have any Tier 2 or 3 techs in atm cause it’s so late. She was clueless as to what I was talking about too so wasn’t any help. Is their a free VPN you can recommend for the time being, Nicole?

Due to individual privacy concerns when selecting this type of service, I won’t be able to recommend any specific VPN. But I’m sure Reddit is full of recommendations.

Same here, NJ and on Verizon. This isn’t the first time this occurred either. This happened around 2 months ago I think? My alternate account goes to SAEL servers and main decides to connect to LAX. Right now I got on ORD1 on main but have a ping of 300 in custom game.

I don’t think Verizon uses Telia routing like these players are having issues with, but I could be wrong. Did you try a traceroute?

I found Telia’s number and am calling them directly. Maybe it will get me somewhere.

I am not really sure what’s going on exactly. but my latency was going over 500 at times. here is the looking glass report

TRACEROUTE:
traceroute to 96.242.229.40 (96.242.229.40), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.373 ms  0.360 ms  0.372 ms
 2  24.105.18.130 (24.105.18.130)  1.069 ms  1.106 ms  1.123 ms
 3  137.221.105.14 (137.221.105.14)  0.807 ms  0.835 ms  0.891 ms
 4  137.221.66.18 (137.221.66.18)  1.389 ms  1.412 ms  1.420 ms
 5  137.221.83.82 (137.221.83.82)  279.358 ms  497.749 ms  497.797 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  5.831 ms  5.847 ms  5.850 ms
 8  4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105)  5.418 ms  5.532 ms  5.508 ms
 9  ae-1-3501.edge7.LosAngeles1.Level3.net (4.69.219.41)  5.690 ms  5.901 ms  5.741 ms
10  TWC-level3-40G.Miami.Level3.net (4.68.62.182)  8.221 ms  8.243 ms  8.246 ms
11  * * *
12  ae203-0.NWRKNJ-VFTTP-319.verizon-gni.net (100.41.209.121)  67.911 ms  66.927 ms  67.016 ms
13  * * *
14  * * *
15  * * *


10/10/2020 02:38:06 UTC
--------------------

TRACEROUTE:
traceroute to 96.242.229.40 (96.242.229.40), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.269 ms  1.176 ms  1.183 ms
 2  37.244.23.131 (37.244.23.131)  1.183 ms  1.184 ms  1.183 ms
 3  24.105.62.152 (24.105.62.152)  0.703 ms  0.709 ms  0.722 ms
 4  137.221.66.10 (137.221.66.10)  23.429 ms  23.451 ms  23.444 ms
 5  * * *
 6  137.221.69.32 (137.221.69.32)  42.346 ms  39.867 ms  39.836 ms
 7  7-1-4.ear7.Chicago2.Level3.net (4.7.196.133)  2.187 ms  2.213 ms  2.210 ms
 8  ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14)  4.253 ms  3.694 ms  3.662 ms
 9  4.68.37.186 (4.68.37.186)  2.584 ms  2.395 ms  2.342 ms
10  * * *
11  ae204-0.NWRKNJ-VFTTP-319.verizon-gni.net (100.41.209.119)  376.980 ms  377.002 ms  376.575 ms
12  * * *
13  * * *
14  * * *
15  * * *


10/10/2020 02:38:06 UTC
--------------------

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

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



10/10/2020 02:38:06 UTC
--------------------

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

--- 96.242.229.40 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3005ms



10/10/2020 02:38:06 UTC
--------------------

MTR:
Start: Sat Oct 10 02:38:06 2020 Blizzard  1.|-- Blizzard                             0.0%    10    0.4   0.3   0.3   0.4   0.0
  2.|-- 37.244.23.131                             0.0%    10    0.4   0.6   0.4   0.8   0.0
  3.|-- 24.105.62.152                             0.0%    10    1.0   1.0   0.8   1.6   0.0
  4.|-- 137.221.66.10                             0.0%    10    1.8   2.0   1.8   2.1   0.0
  5.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  6.|-- 137.221.69.32                             0.0%    10    2.5   2.5   2.3   2.7   0.0
  7.|-- 7-1-4.ear7.Chicago2.Level3.net            0.0%    10    2.1   2.1   2.0   2.5   0.0
  8.|-- ae-1-3510.edge1.Chicago10.Level3.net      0.0%    10    6.4   4.2   2.5   6.8   1.5
  9.|-- 4.68.37.186                               0.0%    10    2.5   2.6   2.5   2.7   0.0
 10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ae204-0.NWRKNJ-VFTTP-319.verizon-gni.net  0.0%    10  356.5 369.3 283.6 466.8  53.2
 12.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0


10/10/2020 02:38:06 UTC
--------------------

MTR:
Start: Sat Oct 10 02:38:06 2020 Blizzard  1.|-- Blizzard                             0.0%    10    0.3   0.4   0.3   0.4   0.0
  2.|-- 24.105.18.130                             0.0%    10    0.7   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.14                            0.0%    10    1.0   1.3   0.8   3.9   0.8
  4.|-- 137.221.66.18                             0.0%    10    0.6   5.3   0.4  27.5  10.1
  5.|-- 137.221.83.82                             0.0%    10  283.5 575.8 128.7 1260. 427.0
  6.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32                             0.0%    10   62.3  17.3   5.9  62.3  22.0
  8.|-- 4-1-3.ear3.LosAngeles1.Level3.net         0.0%    10    5.6   6.2   5.4  11.2   1.7
  9.|-- ae-1-3501.edge7.LosAngeles1.Level3.net    0.0%    10    6.0   6.1   5.6   8.4   0.7
 10.|-- TWC-level3-40G.Miami.Level3.net           0.0%    10    5.9   5.8   5.7   5.9   0.0
 11.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ae203-0.NWRKNJ-VFTTP-319.verizon-gni.net  0.0%    10   67.1  69.8  67.1  90.2   7.1
 13.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0


10/10/2020 02:38:06 UTC
--------------------

The looking glass is having trouble reaching your home connection. Level3 is a routing partner that both Blizzard and ISPs use. After it leaves them and goes to Verizon, you can see the lag start to build. I imagine they are aware of this, but wouldn’t hurt to call it in.

However, I can confirm that you don’t use Telia’s routing services like the OP and followup poster, so if you want to continue discussion, you may want to start a new thread.

Ah I see sorry for deviating from this threads subject in that case. Thank you for the information

No worries. I know everyone is just looking for help and doesn’t know what’s causing their problems :smiley:

I am also in NJ using Verizon. I only have issues with Blizzard Games right now.

Okay, can Verizon players start a new thread instead please? We’re discussing Telia routing issues here :slight_smile:

1 Like

Telia outages:
Aston, NN - outage
Phoenix, AZ - outage

American Subcontractor of Telia that is performing maintenance:
Greenville, pa & Cleveland, Ohio - Affected areas - maintenance being conducted between 10pm est 10/9/20 and 5pm 10/10/20 - Information provided by a Telia tech. He said that the maintenance shouldn’t cause the service to be down the entire time, but the 10pm to 5pm period is the scheduled time.

This probably explains our issues. Also, if the Verizon customers in NJ are using the same American contractor that’s doing maintenance, that’s probably why they’re having the same issue as Telia users.

1 Like