That’s not how networking works. The traffic is bidirectional, otherwise it wouldn’t work at all. Some traffic is getting through, just not enough. This is not all that uncommon in the networking world. I’ve seen it many times over the years.
1 Like
You will note that the Blue stated they may not necessarily recommend it, as it may not necessarily resolve your issue or cause additional problems.
Also, your cell provider (Hotspot) may also use the same network backbone as your ISP, which will not necessarily resolve your issue.
The VPN option can also not work if the other end of it happens to connect to a similar route that is affected, which is why the Blue stated there have been SOME success in using vpn.
1 Like
You are proposing a solution that is risky. Any free VPN or it sells information, or sells my bandwidth. Perfect for an infantile PC, very insecure for a PC of an adult.
You may repair what works badly not to propose to us take a risk.
This game’s not for free we pay the fee.
After many hours of waiting, I’m able to login again, but…What happened to my gears, my transmog, my progression, my quests, my inventory, my bank, my everything? HELLO?
No way my ISP is that buggy!!!
I hear what you are saying, however, I am on CenturyLink (Legacy Qwest) and am having the same trouble as people on FioS. Can you give insight on why that is? Thank you in advance, as you seem to know what you are talking about, and I do not understand 
I’m using a hotspot and have tried tether as well. I can log into one server (garithos), if I join a group or island etc, I get stuck on a loading screen and dc’d.
If I try to login to where I transferred my main earlier this week, I cannot get to the character screen on zero of 4 accounts. I also cannot login to any alts on illidan or stormrage on any of those accounts.
Never had this issue until I tried to login around noon est. worked fine as of 3am est.
Edit: As an update, after trying all day. The second I posted this my character popped up and I could log in. Appears as though I can on other accounts as well. Hope others can log in now as well.
Yup, you are right
ISP from the all around the globe changed someting that made wow crash
1 Like
To those claiming its a verizon issue, I’m still able to play FFXIV and Netflix and HULU AND smart tv. soooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo there’s that. It’s not the interwebz. It’s Blizz.
Thank you for explaining this too me. sh*t
From the UK to Magtheridon with my character in Nazjatar … I’m now logged in and see NPCs and have my pets … joy … now to do dailies (I hope) and skip sleep tonight 
1 Like
Local Network (house) > Local ISP > Local ISP > Backbone services > Backbone services > Blizzard’s ISP > Blizzard’s severs.
There are multiple companies involved in getting your data to an end point. When they say it is an ISP issue, they are avoiding pointing a finger at another company out of professional courtesy.
Depending on what ISP you have, they pay others to take the data and forward it on. For example we once had an issue that lasted 12+ hours on a Sunday where the Cox cable handoff to Blizz was broken. Only Cox players could not get in - but they could get to any other website. Cox had to resolve it. I am NOT saying they are at fault today. Just giving a past example.
YOUR LOCAL ISP is fine if you can connect to most everything else - it is downstream closer to the server you want to connect to. Just like a traffic jam. Using a VPN puts your data on a different road and lets you get to the server.
7 Likes
Sure enough works fine on my T-mobile hotspot. Doesn’t work on my home internet (CenturyLink). Home internet seems to be working for everything else that I’ve tried, just not WoW.
Edit: Home internet working too as of 3 PM PST so I guess it is fixed for me.
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 6 ms 5 ms 5 ms
3 10 ms 13 ms 12 ms
4 16 ms 16 ms 15 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
5 16 ms 14 ms 15 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
6 * 15 ms 16 ms lag-101.ear3.Miami2.Level3.net [4.15.156.29]
7 * * * Request timed out.
8 16 ms 16 ms 16 ms BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
9 50 ms 50 ms 50 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
10 * * * Request timed out.
11 51 ms * * et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
12 50 ms 50 ms 48 ms be2-pe02-eqch2.as57976.net [137.221.69.73]
13 52 ms 52 ms 53 ms 24.105.62.129
Trace complete.thanks… and I just got in… not sure if I will stay in or get booted but I am in <3 9 hours wait…
Does Century link Share the VERIZON backbone? If T-Mobile works and Verizon doesn’t that also explains a lot.
We in boys… at least for now it seems.
Local Network (house) > Local ISP > Local ISP > Backbone services > Backbone services > Blizzard’s ISP > Blizzard’s severs.
There are multiple companies involved in getting your data to an end point. When they say it is an ISP issue, they are avoiding pointing a finger at another company out of professional courtesy.
Depending on what ISP you have, they pay others to take the data and forward it on. For example we once had an issue that lasted 12+ hours on a Sunday where the Cox cable handoff to Blizz was broken. Only Cox players could not get in - but they could get to any other website. Cox had to resolve it. I am NOT saying they are at fault today. Just giving a past example.
YOUR LOCAL ISP is fine if you can connect to most everything else - it is downstream closer to the server you want to connect to. Just like a traffic jam. Using a VPN puts your data on a different road and lets you get to the server.
Thank you for explaining this! I was super confused how in the world it is ISP issue when it is more than one ISP having this trouble!
2 Likes
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms modem.centurylink.net [192.168.0.1]
2 23 ms 43 ms 23 ms fl-184-0-224-3.dhcp.centurylinkservices.net [184.0.224.3]
3 23 ms 64 ms 25 ms 162-104-248-244.wan.centurylink.net [162.104.249.244]
4 * * * Request timed out.
5 * * * Request timed out.
6 169 ms 181 ms 137 ms nap-brdr-01.inet.qwest.net [67.14.29.102]
7 127 ms * 151 ms 63.146.26.138
8 * * * Request timed out.
9 39 ms 39 ms 38 ms BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
10 86 ms 85 ms 85 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
11 86 ms 86 ms 85 ms xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
12 85 ms 87 ms 85 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
13 85 ms 86 ms 130 ms 137.221.65.122
14 85 ms 105 ms 95 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
15 89 ms 86 ms 97 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
16 95 ms 113 ms 90 ms 24.105.30.129
Trace complete.C:\Users\XenoDrake>tracert 24.105.30.129
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 8 ms 6 ms 47.204.202.1
3 19 ms 8 ms 15 ms 172.99.42.174
4 16 ms 20 ms * ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
5 14 ms 13 ms 16 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
6 * 15 ms 16 ms lag-101.ear3.Miami2.Level3.net [4.15.156.29]
7 * * * Request timed out.
8 18 ms 16 ms 17 ms BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
9 * 73 ms 74 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
10 93 ms 70 ms 71 ms xe-0-0-1-1-br01-eqda6.as57976.net [137.221.65.62]
11 73 ms 73 ms 73 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
12 72 ms 73 ms 73 ms 137.221.65.122
13 88 ms 218 ms 218 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
14 82 ms 163 ms 74 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
15 74 ms 73 ms 78 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
16 75 ms 73 ms 76 ms 24.105.30.129
Trace complete.
> BlockquoteMy T-Mobile hotspot doesn’t connect either.