Pork roll, even Taylor has it branded on the box.
Taylor ham! Haha!
I have seen it used both ways though.
Northern NJ here, also on FIOS. Been having similar login issues the past couple days, always stuck at “Logging in to game server”. I was able to get in today at around 5:00pm, but ran into the issue again at 9:00pm. I haven’t tried a VPN yet, but will update if anything changes.
honestly we should probably all be reporting this on the fios server or tweeting their support. Doubt they are reading the wow tech support forums.
1 Like
VPNS do 100% work btw.
North NJ, FIOS Cannot connect tonight, could not connect Saturday after one.
Below is Looking Glass info
TRACEROUTE:
traceroute to 96.225.76.27 (96.225.76.27), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.310 ms 0.335 ms 0.349 ms
2 24.105.18.3 (24.105.18.3) 0.659 ms 0.776 ms 0.869 ms
3 137.221.105.12 (137.221.105.12) 0.901 ms 1.049 ms 1.072 ms
4 137.221.66.16 (137.221.66.16) 2.997 ms 3.028 ms 3.039 ms
5 137.221.83.66 (137.221.83.66) 1.067 ms 1.059 ms 1.067 ms
6 137.221.65.68 (137.221.65.68) 58.866 ms 56.255 ms 56.250 ms
7 137.221.68.32 (137.221.68.32) 6.037 ms 5.993 ms 5.992 ms
8 las-b21-link.telia. net (62.115.178.200) 5.774 ms 5.897 ms 5.903 ms
9 xe-5-3-2.BR3.LAX15.ALTER. NET (152.179.21.77) 5.813 ms 5.861 ms 5.888 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-312.verizon-gni. net (100.41.220.231) 60.977 ms 60.603 ms 62.782 ms
12 * * *
13 * * *
14 * * *
15 * * *
19/11/2019 02:27:07 UTC
TRACEROUTE:
traceroute to 96.225.76.27 (96.225.76.27), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.187 ms 1.237 ms 1.260 ms
2 24.105.18.3 (24.105.18.3) 1.278 ms 1.298 ms 1.317 ms
3 137.221.105.12 (137.221.105.12) 2.428 ms 2.486 ms 2.508 ms
4 137.221.66.16 (137.221.66.16) 2.532 ms 2.574 ms 2.601 ms
5 137.221.83.66 (137.221.83.66) 8.133 ms 8.162 ms 8.181 ms
6 137.221.65.68 (137.221.65.68) 57.201 ms 52.480 ms 52.474 ms
7 137.221.68.32 (137.221.68.32) 6.858 ms 6.211 ms 6.437 ms
8 las-b21-link.telia. net (62.115.178.200) 5.774 ms 5.814 ms 5.831 ms
9 xe-5-3-2.BR3.LAX15.ALTER. NET (152.179.21.77) 5.583 ms 5.601 ms 5.620 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-312.verizon-gni. net (100.41.220.231) 61.069 ms 61.473 ms 61.237 ms
12 * * *
13 * * *
14 * * *
15 * * *
19/11/2019 02:27:07 UTC
PING:
PING 96.225.76.27 (96.225.76.27) 56(84) bytes of data.
— 96.225.76.27 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
19/11/2019 02:27:07 UTC
PING:
PING 96.225.76.27 (96.225.76.27) 56(84) bytes of data.
— 96.225.76.27 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms
19/11/2019 02:27:07 UTC
MTR:
Start: Tue Nov 19 02:27:07 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 20.1 2.7 0.5 20.1 6.1
3.|-- 137.221.105.12 0.0% 10 0.8 1.4 0.7 5.8 1.3
4.|-- 137.221.66.16 0.0% 10 1.2 3.3 0.9 23.5 7.1
5.|-- 137.221.83.66 0.0% 10 6.7 4.5 0.8 7.4 2.5
6.|-- 137.221.65.68 0.0% 10 6.3 16.9 5.7 59.2 20.9
7.|-- 137.221.68.32 0.0% 10 16.6 7.6 5.8 16.6 3.5
8.|-- las-b21-link.telia. net 0.0% 10 5.9 5.7 5.5 6.0 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER. NET 0.0% 10 5.7 5.7 5.6 5.8 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-312.verizon-gni. net 0.0% 10 70.1 61.5 60.5 70.1 3.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19/11/2019 02:27:07 UTC
MTR:
Start: Tue Nov 19 02:27:07 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.6 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 137.221.105.12 0.0% 10 0.7 0.9 0.7 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 1.0 6.9 1.0 31.3 11.7
5.|-- 137.221.83.66 0.0% 10 4.2 10.1 1.5 57.3 16.7
6.|-- 137.221.65.68 0.0% 10 5.7 18.1 5.7 63.1 20.0
7.|-- 137.221.68.32 0.0% 10 6.1 10.6 5.9 32.6 8.3
8.|-- las-b21-link.telia. net 0.0% 10 5.8 6.0 5.5 8.0 0.5
9.|-- xe-5-3-2.BR3.LAX15.ALTER. NET 0.0% 10 11.2 6.3 5.6 11.2 1.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-312.verizon-gni. net 0.0% 10 61.2 61.1 60.4 64.4 1.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19/11/2019 02:27:07 UTC
1 Like
The frequency of disconnects went down the last couple days, but never went away. Today though the disconnects are lasting for longer than before. It’s also strange that sometimes either the chat or the game world disconnects leaving the other intact, so you can either chat or move around still.
Issue has been on and off since last Wednesday.
Haddonfield, NJ
1 Like
I am also in NJ using Fios internet and have been experiencing connectivity issues in Classic for the past couple days. Players running in place, DC’d, then stuck at “Logging in to game server” indefinitely
Just an update for everyone! Used VPN and got in. So temp fix for me but I wont miss raid tonight.
how do you use a vpn?
Exactly my problem! Today seems to be much worse than it has been for some reason. When I get disconnected I just lose the ability to interact with anything in the game. It doesn’t even boot me for disconnection as I have to alt-f4 just to get out of the game.
which VPN? link plz?
i think its expressvpn
Checking in with problems from Central Jersey, around the Asbury Park/Red Bank area, with FIOS
Logged in for about 15 minutes an hour ago, disconnected during a M+, and now I’m perpetually stuck on “Logging in to game server” or black screen at character select
Same for me as well.
Central NJ reporting in…
Had no problems up until about 30min-1hr ago. Everything was working as normal till npc’s and other players began running in place. Tried to log out and quit game from within the client, but had no success. Closed WoW through task manager and have not been able to successfully login since. I am stuck at the “Logging in to game server” prompt. I am trying to log into Sargeras-US.
For completeness sake, I am having no issues logging into WoW classic.
Where is blizzard admin??? lol this is a joke they arent even in here reading or responding
Let me innnnn…
Same.
Strange that we can log in but get stuck at a black screen at character select. Almost as if we are partially logged in. I really hope this gets fixed soon.