Hello,
I have been playing for 1 year with no problems. Getting 2002 today. What does it exactly mean? It is probably problem on my side, right?
Printable View
Hello,
I have been playing for 1 year with no problems. Getting 2002 today. What does it exactly mean? It is probably problem on my side, right?
I'm getting 2002s repeatedly as well. My wife got in fine on PS3 but even reselecting my Data Center and Server hasn't helped me get to the char select. Just constant 2002s.
Just randomly tried a different Data Center on the JP Data Center and I was able to reach the char select no problem. I've tried other NA Data Centers and they don't work so there's something definitely wrong with the Lobby Server at the NA Data Center
Anyone else experiencing this? I'd like to know if this is an actual server side problem or not. I don't want to waste time troubleshooting on my end if it's a problem with the Data Center.
No such issues for me here, and I'm on Midgard also. Just logged back in to check and lobby and game servers were responding just fine... aside from what felt like some inconsistent response times a few times talking to some NPC's in Uldah. We're still having some issues with local nodes being unstable thought, likely the culprit. There's a wider variance than usual in responses during the first 4 hops--on wifi, so some weirdness is expected, but that much swing isn't the norm.
TWC had a lot of local issues this week with service outages and channels locking up and stuff. They're still trying to sort things out on our end from that mess. There's the odd hiccup coming around the NJ/NY segments while within TATA, but it may not be TATA at fault--could be the unstable TWC hops in SC that are only acting up at that point in the route. It isn't too impactful since my latency is still staying low overall. The odd retransmit here and there hasn't been game breaking... yet.
Midardsormr
TWC-SC from Florence SC
Currently partnered with TATA out of Ashburn to get to Montreal (no more sling-shotting Toronto - YAY!)
Code:Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms LPTSRV [10.10.100.1]
2 40 ms 28 ms 23 ms cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 31 ms 25 ms 26 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 14 ms 14 ms 16 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 27 ms 42 ms 27 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 46 ms 35 ms 42 ms 107.14.19.42
7 30 ms 35 ms 33 ms ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 31 ms 33 ms 34 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 60 ms 60 ms 61 ms if-3-2.tcore2.NJY-Newark.as6453.net [216.6.87.10]
10 60 ms 63 ms 73 ms if-4-4.tcore2.NYY-New-York.as6453.net [66.198.111.18]
11 58 ms 58 ms 61 ms if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.46]
12 60 ms 60 ms 65 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
13 68 ms 61 ms 62 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
14 59 ms 58 ms 60 ms 66.198.96.50
15 61 ms 61 ms 62 ms 192.34.76.2
16 63 ms 62 ms 62 ms 199.91.189.234
17 62 ms 60 ms 62 ms 199.91.189.74
Trace complete.
Code:Tracing route to 199.91.189.30 over a maximum of 30 hops
1 2 ms <1 ms <1 ms LPTSRV [10.10.100.1]
2 46 ms 31 ms 15 ms cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 77 ms 18 ms 26 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 15 ms 13 ms 14 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 27 ms 25 ms 26 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 34 ms 34 ms 35 ms 107.14.19.20
7 33 ms 43 ms 34 ms ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
8 31 ms 30 ms 41 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 60 ms 63 ms 62 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.138]
10 58 ms 58 ms 60 ms if-4-4.tcore2.NYY-New-York.as6453.net [66.198.111.18]
11 60 ms 60 ms 61 ms if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.46]
12 62 ms 63 ms 62 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
13 61 ms 63 ms 62 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
14 62 ms 63 ms 62 ms 66.198.96.50
15 63 ms 64 ms 62 ms 192.34.76.2
16 84 ms 63 ms 62 ms 199.91.189.234
17 62 ms 61 ms 63 ms 199.91.189.30
Trace complete.
Code:Ping statistics for 199.91.189.30:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 60ms, Maximum = 79ms, Average = 63ms
I keep getting 2002 as well. I play on PS3 on Aether.