talked with verizon they say its a blizzard server issue. I submitted a ticket on it with the traceroute i did. hopefully they fix it soon… since its the last week of the season and im kinda annoyed i cant do a last second push to 1950 
Lazz- I just spoke to them also. Confirmed on my end it is solid. Reset everything… nothing else they could do.
Hey all,
So far it looks like most of these reports are all Verizon Fios from New Jersey and surrounding areas. We are getting some tracking going. Could we get some looking glass tests for routing data? Normally I would ask for a winMTR test also but typically that ISP (Verizon Fios) doesn’t work with the test. Pingplotter might work but that tool is more difficult to use. For assistance with Pingplotter setup please reach out to the software developers of the tool.
Once you have the results of either Looking Glass or Pingplotter, please post the results here. Put three ~ marks before the copy paste so it puts it in a separate text box. It should look something like:
~~~
Test results here
TRACEROUTE:
traceroute to 173.54.241.5 (173.54.241.5), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.466 ms 0.442 ms 0.437 ms
2 24.105.18.2 (24.105.18.2) 3.123 ms 3.308 ms 3.330 ms
3 137.221.105.14 (137.221.105.14) 1.423 ms 1.423 ms 1.418 ms
4 137.221.66.22 (137.221.66.22) 0.652 ms 0.661 ms 0.689 ms
5 137.221.83.86 (137.221.83.86) 363.190 ms 580.807 ms 580.873 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.005 ms 5.994 ms 6.398 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.611 ms 5.656 ms 5.798 ms
9 4.69.219.45 (4.69.219.45) 5.795 ms 5.682 ms 5.667 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 12.323 ms 12.307 ms 12.295 ms
11 100.41.27.245 (100.41.27.245) 64.868 ms 64.891 ms 64.889 ms
12 * pool-173-54-241-5.nwrknj.fios.verizon.net (173.54.241.5) 64.504 ms 64.648 ms
21/02/2022 00:04:17 UTC
--------------------
PING:
PING 173.54.241.5 (173.54.241.5) 56(84) bytes of data.
64 bytes from 173.54.241.5: icmp_seq=1 ttl=51 time=63.2 ms
64 bytes from 173.54.241.5: icmp_seq=2 ttl=51 time=60.7 ms
64 bytes from 173.54.241.5: icmp_seq=3 ttl=51 time=60.7 ms
64 bytes from 173.54.241.5: icmp_seq=4 ttl=51 time=60.7 ms
--- 173.54.241.5 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 60.730/61.365/63.219/1.112 ms
21/02/2022 00:04:17 UTC
--------------------
MTR:
Start: Mon Feb 21 00:04:17 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.4 0.5 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 0.7 0.5 1.2 0.0
3.|-- 137.221.105.14 0.0% 10 1.1 1.1 1.0 1.4 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 0.7 0.5 0.9 0.0
5.|-- 137.221.83.86 0.0% 10 1049. 552.6 45.8 1198. 418.9
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 21.2 6.0 101.4 33.0
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.8 5.7 5.5 6.0 0.0
9.|-- 4.69.219.45 0.0% 10 5.8 6.6 5.6 13.0 2.2
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.5 7.5 6.4 11.6 1.6
11.|-- 100.41.27.245 0.0% 10 61.1 61.0 60.8 61.6 0.0
12.|-- pool-173-54-241-5.nwrknj.fios.verizon.net 0.0% 10 60.8 61.0 60.8 61.3 0.0
21/02/2022 00:04:17 UTC
--------------------TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.663 ms 1.628 ms 1.634 ms
2 24.105.18.2 (24.105.18.2) 1.640 ms 1.638 ms 1.636 ms
3 137.221.105.14 (137.221.105.14) 1.635 ms 1.633 ms 1.632 ms
4 137.221.66.18 (137.221.66.18) 1.596 ms 1.595 ms 1.592 ms
5 137.221.83.82 (137.221.83.82) 1061.185 ms 1061.239 ms 1061.708 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.324 ms 6.658 ms 6.702 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.764 ms 5.711 ms 5.821 ms
9 4.69.219.45 (4.69.219.45) 5.824 ms 5.781 ms 5.788 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 6.528 ms 6.294 ms 6.242 ms
11 100.41.27.247 (100.41.27.247) 60.069 ms 60.264 ms 60.136 ms
12 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 60.637 ms 60.720 ms 61.184 ms
20/02/2022 23:12:53 UTC
--------------------
TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.073 ms 1.073 ms 2.451 ms
2 24.105.18.2 (24.105.18.2) 2.503 ms 2.521 ms 2.522 ms
3 137.221.105.14 (137.221.105.14) 3.178 ms 3.194 ms 3.195 ms
4 137.221.66.18 (137.221.66.18) 2.459 ms 2.472 ms 2.475 ms
5 137.221.83.82 (137.221.83.82) 934.541 ms 1162.426 ms 1162.466 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.971 ms 6.070 ms 5.998 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.564 ms 5.673 ms 5.664 ms
9 4.69.219.45 (4.69.219.45) 5.618 ms 5.794 ms 5.622 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 6.360 ms 6.277 ms 6.249 ms
11 100.41.27.247 (100.41.27.247) 60.997 ms 60.945 ms 61.420 ms
12 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 62.138 ms 61.936 ms 61.384 ms
20/02/2022 23:12:53 UTC
--------------------
TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.373 ms 0.351 ms 0.351 ms
2 24.105.18.2 (24.105.18.2) 0.583 ms 0.686 ms 0.810 ms
3 137.221.105.14 (137.221.105.14) 1.319 ms 1.329 ms 1.329 ms
4 137.221.66.18 (137.221.66.18) 0.710 ms 0.720 ms 0.756 ms
5 137.221.83.82 (137.221.83.82) 1233.829 ms 1233.891 ms 1234.757 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.882 ms 6.145 ms 6.239 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.618 ms 5.625 ms 5.718 ms
9 4.69.219.45 (4.69.219.45) 5.722 ms 5.645 ms 5.715 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 6.401 ms 6.429 ms 6.221 ms
11 100.41.27.247 (100.41.27.247) 61.049 ms 61.001 ms 61.005 ms
12 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 61.360 ms 61.224 ms 61.042 ms
20/02/2022 23:12:53 UTC
--------------------
TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.403 ms 0.375 ms 0.373 ms
2 37.244.23.3 (37.244.23.3) 1.294 ms 1.302 ms 1.300 ms
3 24.105.62.152 (24.105.62.152) 0.991 ms 1.007 ms 0.969 ms
4 137.221.66.14 (137.221.66.14) 1.237 ms 1.236 ms 1.233 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.022 ms 2.156 ms 2.118 ms
7 chi-b23-link.ip.twelve99.net (62.115.178.248) 1.235 ms 1.237 ms 1.354 ms
8 verizon-ic349653-chi-b23.ip.twelve99-cust.net (62.115.180.11) 1.837 ms 1.907 ms 1.879 ms
9 100.41.27.245 (100.41.27.245) 20.890 ms 20.876 ms 20.849 ms
10 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 20.414 ms 20.527 ms 20.533 ms
20/02/2022 23:12:55 UTC
--------------------
TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.462 ms 0.449 ms 0.448 ms
2 37.244.23.3 (37.244.23.3) 0.619 ms 0.686 ms 0.744 ms
3 24.105.62.152 (24.105.62.152) 1.743 ms 1.758 ms 1.758 ms
4 137.221.66.14 (137.221.66.14) 1.243 ms 1.262 ms 1.269 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 63.502 ms 57.753 ms 57.696 ms
7 chi-b23-link.ip.twelve99.net (62.115.178.248) 42.938 ms 38.371 ms 38.405 ms
8 verizon-ic349653-chi-b23.ip.twelve99-cust.net (62.115.180.11) 2.074 ms 2.085 ms 2.080 ms
9 100.41.27.245 (100.41.27.245) 21.046 ms 20.917 ms 20.893 ms
10 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 21.204 ms 21.176 ms 21.251 ms
20/02/2022 23:12:58 UTC
--------------------
MTR:
Start: Sun Feb 20 23:12:53 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.4 2.2 0.4 18.6 5.7
2.|-- 24.105.18.2 0.0% 10 0.6 0.8 0.6 1.0 0.0
3.|-- 137.221.105.14 0.0% 10 1.0 1.1 1.0 1.5 0.0
4.|-- 137.221.66.18 0.0% 10 0.8 0.7 0.5 0.9 0.0
5.|-- 137.221.83.82 0.0% 10 34.2 503.4 34.2 1157. 420.8
6.|-- 137.221.65.68 90.0% 10 13500 13500 13500 13500 0.0
7.|-- 137.221.68.32 0.0% 10 5.9 18.5 5.9 56.2 16.9
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 6.0 5.7 5.6 6.0 0.0
9.|-- 4.69.219.45 0.0% 10 7.0 7.9 5.8 15.5 3.6
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.6 6.7 6.4 7.5 0.0
11.|-- 100.41.27.247 0.0% 10 60.3 60.7 60.1 64.2 1.1
12.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 61.1 61.5 60.9 62.3 0.0
20/02/2022 23:12:53 UTC
--------------------
MTR:
Start: Sun Feb 20 23:12:53 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.5 0.3 1.2 0.0
2.|-- 24.105.18.2 0.0% 10 0.9 0.8 0.6 1.2 0.0
3.|-- 137.221.105.14 0.0% 10 0.9 1.0 0.8 1.4 0.0
4.|-- 137.221.66.18 0.0% 10 1.0 0.7 0.5 1.0 0.0
5.|-- 137.221.83.82 0.0% 10 1409. 716.9 155.9 1409. 419.8
6.|-- 137.221.65.68 80.0% 10 13280 13400 13280 13520 169.6
7.|-- 137.221.68.32 0.0% 10 22.9 7.9 5.9 22.9 5.3
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.5 5.7 5.5 6.6 0.0
9.|-- 4.69.219.45 0.0% 10 5.5 7.6 5.5 14.1 3.0
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.3 6.5 6.3 6.9 0.0
11.|-- 100.41.27.247 0.0% 10 60.2 60.2 60.1 60.4 0.0
12.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 61.3 61.3 60.5 62.1 0.0
20/02/2022 23:12:53 UTC
--------------------
MTR:
Start: Sun Feb 20 23:12:53 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.6 0.4 0.8 0.0
2.|-- 24.105.18.2 0.0% 10 1.0 0.9 0.7 1.1 0.0
3.|-- 137.221.105.14 0.0% 10 1.2 1.2 1.0 1.5 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 0.9 0.7 1.2 0.0
5.|-- 137.221.83.82 0.0% 10 1409. 717.2 156.3 1409. 419.9
6.|-- 137.221.65.68 80.0% 10 13280 13400 13280 13519 169.1
7.|-- 137.221.68.32 0.0% 10 23.4 8.0 6.0 23.4 5.4
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.7 5.8 5.5 6.9 0.0
9.|-- 4.69.219.45 0.0% 10 5.7 7.1 5.6 14.3 2.8
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 6.4 6.5 6.4 6.9 0.0
11.|-- 100.41.27.247 0.0% 10 60.4 60.3 60.1 60.7 0.0
12.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 61.6 61.5 60.6 62.4 0.0
20/02/2022 23:12:53 UTC
--------------------
MTR:
Start: Sun Feb 20 23:12:55 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.23.3 0.0% 10 0.6 0.5 0.4 0.8 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 1.0 0.7 1.2 0.0
4.|-- 137.221.66.14 0.0% 10 1.1 1.1 1.0 1.3 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.1 4.4 1.9 22.9 6.5
7.|-- chi-b23-link.ip.twelve99.net 0.0% 10 1.5 3.4 1.3 21.1 6.2
8.|-- verizon-ic349653-chi-b23.ip.twelve99-cust.net 0.0% 10 2.0 3.4 1.8 16.7 4.7
9.|-- 100.41.27.245 0.0% 10 21.0 21.7 20.8 23.9 0.9
10.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 21.5 21.1 20.4 21.9 0.0
20/02/2022 23:12:55 UTC
--------------------
MTR:
Start: Sun Feb 20 23:12:55 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.3 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 0.9 0.8 1.1 0.0
4.|-- 137.221.66.14 0.0% 10 1.1 2.0 1.0 10.2 2.8
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.0 7.8 1.9 35.6 12.4
7.|-- chi-b23-link.ip.twelve99.net 0.0% 10 1.4 1.4 1.2 1.6 0.0
8.|-- verizon-ic349653-chi-b23.ip.twelve99-cust.net 0.0% 10 26.4 4.3 1.8 26.4 7.7
9.|-- 100.41.27.245 0.0% 10 20.8 21.2 20.8 22.4 0.3
10.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 21.2 21.2 20.2 22.2 0.5
20/02/2022 23:12:55 UTC
--------------------
TRACEROUTE:
traceroute to 173.70.104.113 (173.70.104.113), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.359 ms 0.343 ms 0.343 ms
2 37.244.23.3 (37.244.23.3) 0.566 ms 0.679 ms 0.882 ms
3 24.105.62.152 (24.105.62.152) 1.737 ms 1.753 ms 1.754 ms
4 137.221.66.14 (137.221.66.14) 1.091 ms 1.121 ms 1.126 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 16.352 ms 12.773 ms 12.749 ms
7 chi-b23-link.ip.twelve99.net (62.115.178.248) 1.550 ms 1.534 ms 1.514 ms
8 verizon-ic349653-chi-b23.ip.twelve99-cust.net (62.115.180.11) 1.794 ms 1.806 ms 1.805 ms
9 100.41.27.245 (100.41.27.245) 20.849 ms 20.850 ms 20.830 ms
10 pool-173-70-104-113.nwrknj.fios.verizon.net (173.70.104.113) 21.593 ms 21.584 ms 21.563 ms
20/02/2022 23:13:08 UTC
--------------------
MTR:
Start: Sun Feb 20 23:13:00 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.6 0.5 1.1 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 0.9 0.8 1.0 0.0
4.|-- 137.221.66.14 0.0% 10 1.2 1.2 1.0 1.3 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.0 6.7 2.0 32.2 9.6
7.|-- chi-b23-link.ip.twelve99.net 0.0% 10 1.4 1.5 1.4 1.7 0.0
8.|-- verizon-ic349653-chi-b23.ip.twelve99-cust.net 0.0% 10 2.0 2.6 1.8 7.7 1.8
9.|-- 100.41.27.245 0.0% 10 20.8 21.2 20.8 23.6 0.7
10.|-- pool-173-70-104-113.nwrknj.fios.verizon.net 0.0% 10 20.4 21.0 20.2 22.4 0.5
20/02/2022 23:13:00 UTC
--------------------received a blizzard response saying that people have used vpns to handle the situation. Anyone seen this working yet?
Hey Lazzarros,
They said same to me, but not sure how VPN will solve issue? No to mention most you need to pay for or get throttled etc.
I tried Hotspot from phone but way too slow for long testing.
VPN’s route you a different path than your ISP does is why it is a possible short term remedy. VPN’s, while able to be used, are unsupported by Blizzard.
1 Like
Hey Kald_ any updates on all our items? Our shared lookingglass data?
Throwing my hat in this as well. I did everything: scan, repair, flushed dns, renewed ip, reset my router, disabled my firewall, deleted addons, wtf, and cache, uninstalled and reinstalled the game completely, disabled things on startup, updated my graphics drivers, checked to see if my firmware drivers were up to date, disabled network optimization ingame, I even reformatted my computer but nothing fixed the issue.
Normally I wouldnt care too much for a dungeon but this has made me lose arena games simply because I fail to load in and that is quite frustrating.
The only things that have actually been working for me is 1. a VPN and 2. phone tethering. I tried to replicate the error when I was connected to those two things for 20 minutes straight and nothing, as soon as I switched back within the first minute of spamming load screens trying to zone into the stockades I got ‘Transfer Aborted: Instance not found’.
I did submit an ingame ticket with MSInfo, WinMTR, tracer route, DxDiag, and pathping. But not much could be done as I think it’s on Verizon’s end personally, no idea how to fix but just wanted to share my experience and the two ways I’ve found to work around the issue for now. I was able to queue arena last night with no errors while on a VPN.
*Edit: Also wanted to say from NJ with Verizon Fios
1 Like
I feel for you man. I just tried again now, 4th game, kicked me to login screen exiting arena. Guess done for the day again… too frustrating lol
temp fix I got NORDVPN and haven’t gotten an abort since 
blizzard should really fix their game tho…
Which would indicate that the issue is with your normal connection, as the service works with other connections.
This seems to be an issue with Verizon fios in the northeast every so often, and it always cubed back to being verizon’s issue.
2 Likes
Yo slip- curious. What speeds are you getting through the Nordvpn? I was getting like 800/900 up and down, before. I know it doesnt need to be that high, but interested to see how much slower it will be with a VPN. Blizzard should refund us the cost 
Why would they do that? Blizzard isn’t having the issue, FiOS is. When using a VPN works and connects you to WoW, it proves the issue is in the ISP’s network. They likely have a bad connection between their nodes heading to Blizzard.
2 Likes
Because it is only the connection to blizzard I can play any other game fine so why am I paying 15$ for a game where I get constant transfer aborts and need a VPN to play? Literally can’t even add an enter battle button for rated battlegrounds when you get an instance abort so you could rejoin yet you’re somehow still locked to the instance… Also Transfer Aborts have been in wow for 12+ years kinda jokes it’s never been fixed
1 Like
Then contact your ISP and gripe at them to fix the issue. It is their issue, not Blizzards when your ISP is the one who contracts with other companies to send the signals to different locations.
3 Likes
That isn’t how you find the company responsible. Your connection looks something like this:
Your ISP → routing peer the ISP pays → possible secondary routing peer → Blizzard routing peer → game servers
You can skip over some of the hops owned by the 1st, 2nd, or 3rd parties listed above by using a VPN. Since other players in your area on the same ISP are confirming this method works, it confirms that the problem is FiOS or its peers.
Blizzard has no control over the FiOS network or peers. But you, as a paying customer of FiOS, have grounds to raise this concern with the ISP’s support team. They likely know about it already, but adding your complaint to the pile may expedite the fixes.
Until internet access across the globe is absolutely perfect (never going to happen), a problem like this will continue to pop up in-game and as a topic in the forum.
2 Likes
Just chiming in with the same problem. It started when I was doing the holiday dungeon last week, Would leave instance, but it would just put me back in Shadowfang Keep. Then trying to log into certain characters I would get a “world server down” message. This is still happening. In addition, after arriving at flight points I will stay mounted in the air for an extended period of time, then get a loading screen, then back at flight master with “instance not found” message.
As I stated I can play any other game other than wow completely fine it’s the routing to the blizzard servers as I said but you obviously just can’t comprehend English unlucky. Then you restate your first statement which further proves my point by agreeing with me that a VPN works to skip the bad nodes and connect into the game. I also then give u a solution to resolve instance aborts by adding a button to rejoin battle as long as the instance is open, then u finish it off with a solid, “need perfect internet to stop instance aborts”. No wonder this game is a joke look who they have working at blizzard LOL… As I said why am I paying 15$ a month for a game I need a VPN to play?