9002 Errors still aren't solved...big waste of money so far.
Error code 2002 and 90000
Printable View
-
07-03-2015, 01:57 PMNoxNebula
-
07-07-2015, 07:49 PMMikotoKanzaki
I'm getting error 2002 as we speak. So frustrating.
Game instantly crashes after the error appears. This happens to me after every single maintenance. -
07-10-2015, 09:18 AMDarkB
Hello. i'm getting this error 2002, cannot connect to Data servers. When it does my character isnt there anymore, just blank. I have to quit the game launcher.
This is a huge issue, i just bought heavensward and cant play.
Gosh i played for hours without a problem now i cannot log in back in game anymore... Come on...
it looks like http://forum.square-enix.com/ffxiv/t...s-%28Jul.-4%29 isnt resolved yet..
Recovery from All Primal Data Center Worlds Technical Difficulties (Jul. 4) -
07-10-2015, 04:34 PMHuunia
I'm on Balmung and I haven't been able to get on for a day now. Constant 2002 errors and I can't even get to my character screen.
-
07-13-2015, 03:20 AMfarcrowe2002 error constantly
Yeah now I'm getting the 2002 error on every data center I have tried (all of them).
Sure wish this problem would get straightened out. -
07-13-2015, 05:06 AMNeophyte
Me too. Got thrown out from Alexander raid and can't relog since then.
-
07-13-2015, 05:44 AMGoruDan
I was playing for hours today no problem. Suddenly I'm out of the game and can't get back in for over an hour. Try changing DNS settings etc. I've been playing mmos for years and this is the first game I've had this type of connectivity error. I already have one guildie canceled his sub for this error, I might not be far behind.
-
07-13-2015, 05:59 AMTheTen
Same here, 90k disconnect, and now I get 2002 on nearly every data center.
-
07-13-2015, 06:16 AMerulisse
same, got back home, and 2002... can get on some data centers, but not on the one i want...
-
07-13-2015, 08:10 AMNeophyte
1h after last one, again 2002/9002/10105 along with ~1000 other players (according to queue).
-
07-17-2015, 03:28 PMVraeliaValkyria
90ked two times in a row, then 2002 error. Gotta love this....
EDIT: Another 2002 error trying to log back in. ._.
EDIT EDIT: 3 90ks, followed by 2 2002 errors. <.<
Please SE, fix this!!!!! -
07-17-2015, 10:01 PMMXMoondoggie
This is happening to me all the time since the latest patch. I used to have the same problem but I fixed my firewall allowances and it solved it but since the patch I get DC randomly again. It's nothing on my end it's like the server is just kicking me for no reason.
Most commonly this happens in A4 just after everyone loads in and the duty commences but it's happened to me in other areas too like the Mist housing area and when it does this it's twice in a row 5 minutes apart. This normally happens late at night between 11pm-Midnight GMT. -
07-18-2015, 01:06 AMRythulian
I've had nothing but 90002 errors today.
Usually when I hit a 90k problem I know what's causing it. It's usually my router playing up and the problem is notable across other devices. Not so much the case today. My router has been stable across other devices and even other online games on my PS4. FFXIV seems to be the only game having problems today.
I've already restarted my router once in the vain hope that it would resolve the problem. It didn't. As far as I can tell there's no logic behind the time frame that's it's happening since the server i'm on is more or less deserted during the hours I play. -
07-18-2015, 02:57 AMRizzard
For the last 3 days I could not play. Myself and my brother are on the ps3 and every time we try to get into the game it gives us the error code 2002 and 90000 and something. We sometimes can get into the game, but can only stay on for almost a minute. That being said it could also be a psn error because it keeps disconnecting us from the psn as well. It all started for us when the game went down for emergency Matinance on the 14th. Is this going to get fixed or what?
-
07-18-2015, 12:18 PMVraeliaValkyria
On top of the 90ks, and the 2002 errors. The lag is freaking unbearable. as I keep..yes, KEEP saying. It's ridiculous. I can't even play due to this. ._.
As a subscriber, it is my right to demand that this be fixed. Yes, I understand, it isn't my game nor do I have any type of control over it. But, since I pay to play, things should be worked on and fixed. This has gone on way too long now. Not only for myself, but for a lot of others are having these problems. I honestly do not care if you have to take the game down for maintenance for a whole freaking day to fix these errors. In fact, I welcome it. If me and others are complaining about things being wrong, then things should be getting fixed. I am pretty sure 99% of the players would not mind waiting a whole day for maintenance to get things fixed within this game. I find it horribly selfish too, that Alexander raid gets an emergency maintenance, whereas these problems (90ks, 2002, and the lag) are by far bigger than Alexander. These problems should be fixed first, above all else. If players cannot play, then things like content is useless.
EDIT: I apologize if I am offending. -
07-21-2015, 02:09 AMNationalcity
What's funny is that I've had 90k since the open beta and still hasn't been addressed I go 90k at least once or twice a day.... I've tried everything listed to fix this error including changing ISP's. It's a problem on there end not mine and I don't think there ever gonna address it I mean look at the first page of both technical forums everything is 90k or 2002 I just don't think they actually know what's wrong. Or maybe they just figure since most of the people are not having problems whoopty do for the rest of us.....
-
07-26-2015, 03:34 PMMaylin
I, too, am also experiencing major issues concerning errors 90k and 2002 disconnections. Upon returning to the game after a 3 month break, I have disconnected well over 20 times in the first day. At first, I would just disconnect in a random place or cutscene, and now, I disconnect from dungeons, as well.
At this point, the game is nearly unplayable. Gathering and exploring new areas are about the only things I can do.
For those who are getting these problems, it would only be logical that they get compensated for not being able to play the game how it's meant to be played. -
07-27-2015, 12:43 AMRaist
It's a networking issue in route to the servers. Need to get with your ISP to properly investigate and make the necessary corrections to provide a more stable route. I have over 125 days worth of playtime (Total Play Time: 125 days, 4 hours, 45 minutes)...would not have that much playtime if I hadn't brought my ISP in to address my problems last year.
Can usually test/prove this through the use of a VPN service. During the free trial you can try multiple locations to tunnel through. When you find one that is stable you can take a snapshot of the route through a tracert, then do another snapshot while on the route your ISP assigns and submit them for review. Should be enough information for them to work from to figure out what is going on and make adjustments.
Mileage may vary on the initial progress...it may take some persistence to get them moving on it, but it is a known problem and has been proven that the ISP's have ways to improve your stability. Don't settle for the usual "no" and "not our problem" responses. When changing the route via a VPN resolves it---it proves it CAN in fact be corrected through the routing policies. That is basically the benefit of what a VPN does--allows you to alter/bypass the parameters of the routing that are negatively impacting your sessions. -
07-28-2015, 02:35 AMT2teddyThanks for all the many times you try to help people, Raist, however the majority of what you said may as well be an alien language to people like me who pretty much only know how to turn on a pc and surf or play a game. :confused::confused:Quote:
Originally Posted by Raist
-
07-28-2015, 06:45 AMRaistLean on your ISP for help, or pull in a tech savvy friend... or follow one of the many guides that have been posted here repeatedly (both user made and links to published material). Here is one such guide from Blizzard I've linked often:Quote:
Originally Posted by T2teddy
https://us.battle.net/support/en/art...g-a-traceroute
Here are the registered names for the Canadian Lobby servers that can be used for testing:
neolobby02.ffxiv.com
neolobby04.fxiv.com
neolobby06.ffxiv.com
Installing and configuring a VPN will be covered by those providing the service...but it is usually fairly simple--often a self-contained installer or a how-to guide to set it up with Windows own connection manager. You set the location to connect to (or enter the appropriate address in the Windows manager), click the button that makes the connection, then play as normal.
Things are fine for far too many people for it to be strictly a server based issue. Routing issues are a known problem in general for web based services and also have been proven to be at fault with XIV quite often. It needs to be flushed out....no matter how good the servers are running, a bad route can make the game unplayable. -
07-28-2015, 12:23 PMTendoFg
Having similar issues. I've been playing since 1.0 and have had absolutely no connectivity problems from then, right up until a month or so ago. The problem intensified when they disabled the auto d/c function.
My 90002 errors started off as an infrequent annoyance but have recently increased in frequency to a point where i can't play for more than an hour or two without disconnecting.
I've gone into my router settings and forwarded the ports outlined in various guides and they have had little to no effect.
People seem nearly 50 % divided on whether it's an ISP issue or a server side issue with the game but I'm pretty sure(although can't be 100 % certain) that it's not ISP related because surely these problems would have occurred a lot sooner than they have and I play a lot of other games online without problem. The fact I've never had these issues before a month ago with FF XIV leads me to believe it's something that's been implemented server side recently.
Regardless, many many people are having these problems now and the number of people complaining over the past couple of weeks has risen substantially. I really don't want to stop playing FF XIV as i play it nearly daily but with these connection issues, i just can't get myself motivated to do anything worthwhile in game for fear of 90k. -
07-29-2015, 05:18 AMWyvrex
I've seen this issue everywhere online, from people on PC and consoles, all over the world - this is definitely not the problem of individual people's internet, not when the issue is so widespread (one or two maybe, but not thousands, just check out how many threads there are on this one topic just on this forum's support pages, there is one on the 'looking into' section of over 200 pages!). If it were an ISP thing, there would be loads of people offering a working solution, but nothing people have tried has seemed to make it stop. Basically, there are hundreds of threads about this one issue with no answers in sight :(
I thought yesterday's maintenance would fix it, but it seems to have made it worse as now I'm getting thrown out every few minutes instead of every 30 mins or longer. Just now was the last straw - got thrown out at the end of a long single player duty for my level 60 class quest and there is no way I'm going back in for fear of 90002 error - also means I can't do the dungeons :(.
It's looking like I'm gonna have to give up on doing anything significant on this game until it's fixed :( which sucks coz I was planning on doing an eternal bond in the next few weeks - no way the server is gonna hold for that length of time!
I've been playing the game for over 6 months with no previous error - seems to have been since 3.05 was installed :S my husband is also playing on PS4 and gets d/c'd.
Please fix this squeenix, I love playing this game too much to give it up now! -
07-29-2015, 05:37 AMLisburn
I am also having 90002 errors constantly which is annoying as I have pretty limited time to play due to long work hours. These started roughly the 23rd July and have started to be more frequent each day since. I love this game so some guidance or fixes would be awesome.
It is most definitely not my ISP as that has been checked thoroughly. -
07-29-2015, 07:14 AMRaistMust be new here... or at least new to this issue on these forums.Quote:
Originally Posted by Wyvrex
It has been repeatedly demonstrated how people have resolved the issues by getting a more stable route established--be that via VPN, working with their ISP, or from the congestion subsiding over time. There was even a thread here in recent weeks where it was disclosed there were downed nodes in the south east affecting scores of players--it was the exact same symptoms. People reported resolving the matter in the short-term by using a VPN service to route away from the failing hops until services were restored.
The issues frequently show up in multiple forums for games and other services. The last mile ISP's routinely get taken to task over it on their own forums. It shows up regularly at composite sites like the dslreports forums and tracking sites like downdetector.com and such. There have been filings with the FCC over the issues. It was a major point brought up in the net neutrality debates. It was also brought up frequently in the TWC/Comcast merger discussions as well. There have been studies and blog posts done on the matter for years. The threat of the congestive failures have been there for decades--there were even checks and balances built into the TCP/IP protocol to fight the issue.
It is nothing new. Perhaps new to you, but not to the community and certainly not to the industry. The problem is that the public has not been properly informed on the matter...and the ISP's get away with overselling bandwidth (not to mention overpricing it in many cases). Most people don't even understand that they mistakenly are calling their bandwidth plan their speed...they've all been duped by their ISP's for far too long.
I and others have posted scores of information on the matter from various sources. Gonna copy/paste a previous post from another thread in hopes it might lead to a better understanding of what may actually be causing these connectivity/stability problems for many of you guys:
http://forum.square-enix.com/ffxiv/t...=1#post3149203
Quote:
Knowledge is empowering....
“Chicken” | A Game Played as a Child and by some ISPs with the Internet
Observations of an Internet Middleman
When the Middleman and ISP are Aligned
Heads ISPs Win, Tails You Lose (And a way to fix it)
Verizon’s Accidental Mea Culpa
“Not” Neutrality?
Running a Trace Route (a how-to from Blizzard for investigating problems)
Lobby server addresses in Canada that can be used for testing in case you don't have the actual IP address you use when playing the game:
neolobby02.ffxiv.com (this is Aether, unsure which of the other two is on what address)
neolobby04.ffxiv.com
neolobby06.ffxiv.com
A site that tracks the status of lots of services---major ISP's and services like Hulu, PSN, XBL, etc., along with links to a couple ISP's pages for convenience
https://downdetector.com/companies
https://downdetector.com/status/comcast-xfinity
https://downdetector.com/status/att
https://downdetector.com/status/time-warner-cable
Site with internet usage statistics. Note, this is the company that mirrors our patches for SE. They are really big on network optimization, and track all kinds of stats on the web.
http://www.akamai.com/html/technolog...try/index.html
http://www.akamai.com/html/technolog...b-monitor.html
http://www.akamai.com/html/technolog...b-metrics.html
Now go forth minions... take your ISP's to task and demand they fix your broken internet!
All kidding aside. There are known issues with North America's infrastructure that lead to the very issues you guys are constantly complaining about. Those who are in the know understand the pitfalls, and have been able to go after their ISP's and get things cleaned up. The only thing separating them from you is a little better understanding of how things work, how to spot the signs of the known problems, and how to best go about seeking help. Hopefully the links up near the top will serve as a means to that end in providing you a basic understanding of the problem, and how you can track/document the signs so you can forward good information to the proper people at your ISP to get a proper assessment that <hopefully> will result in them getting the problems addressed.
Alternatively... you could just try some VPN services (most have some manner of free trial or free use policy you can use for testing---is a good way to demonstrate the issue to your ISP as well). Most will allow you to tunnel to different locations, allowing you to select alternate routes on demand to find a more stable path.
-
07-29-2015, 08:28 AMAlexika
Raist, at first I was really thinking you may be right, but I don't think our ISP is to blame at all. I have done numerous long term pings now to my server and the problem does not arise until it leaves my ISPs network. In fact, the majority of my packet loss is actually once it hits SEs network. I am starting to believe that SE is not paying for enough bandwidth.
-
07-29-2015, 08:48 AMRaistDidn't you previously state you were seeing issues at an alter.net hop? More specifically, I think it was alter.net and LEvel3 if I remember correctly. Alter.net is Verizon. More specifically, Verizon Business. They are the ones opting to put you on Level3 and not someone else. It is all on your ISP's routing policies making that happen...and they have the power to change it if they aren't going to work with Level3 to track down/address the issues with that peering partner.Quote:
Originally Posted by Alexika
It is well within your ISP's power to find you a better route.
Edit: let's see if I can find some examples of what I'm talking about...going back a over a year (03/2014), we have this, where I was wrangling with a localized issue with a TWC gateway (problem was an outdated CMTS):
http://forum.square-enix.com/ffxiv/t...=1#post1918510
I continued to work with them for quite a while...eventually started working more directly with engineering on it (Tier3), as noted in this post:Quote:
Tracing route to 199.91.189.25 over a maximum of 30 hops
1 2 ms <1 ms 1 ms LPTSRV [10.10.100.1]
2 296 ms 65 ms 25 ms cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 11 ms 11 ms 17 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 33 ms 30 ms 24 ms xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
5 33 ms 34 ms 32 ms 107.14.19.44
6 28 ms 40 ms 30 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 33 ms 43 ms 35 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 36 ms 32 ms 34 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41.206]
9 45 ms 42 ms 44 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
10 42 ms 43 ms 61 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
11 66 ms 67 ms 71 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
12 62 ms 61 ms 60 ms 38.122.42.34
13 46 ms 45 ms 46 ms 192.34.76.10
14 42 ms 43 ms 43 ms 199.91.189.242
15 43 ms 44 ms 46 ms 199.91.189.25
Trace complete.
http://forum.square-enix.com/ffxiv/t...RV#post2044489
Eventually, they managed to reign things in a bit at that gateway as shown in the trace in this post:Quote:
Tracing route to 199.91.189.31 over a maximum of 30 hops
1 2 ms <1 ms 1 ms LPTSRV [10.10.100.1]
2 * * * Request timed out. (98.25.64.1, engineering investigating for residential in Florence, SC--seen 1000ms+ lag spikes at times)
3 12 ms 14 ms 12 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5] (Summerville, SC... was previously Raleigh)
4 25 ms 22 ms 32 ms 24.93.64.128 (Charlotte, NC--new Gbit fiber rolled out for Central Charlotte in the last year)
5 31 ms 31 ms 29 ms 107.14.19.42 (Cary, NC-- new Gbit market opening up, AT&T awaiting local boards to approve Residential services)
6 28 ms 32 ms 30 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 37 ms 33 ms 35 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 34 ms 34 ms 36 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
9 39 ms 40 ms 42 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
10 44 ms 44 ms 42 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
11 65 ms 66 ms 65 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
12 59 ms 57 ms 62 ms 38.122.42.34
13 50 ms 44 ms 47 ms 192.34.76.10
14 47 ms 48 ms 46 ms 199.91.189.242
15 44 ms 44 ms 47 ms 199.91.189.31
Trace complete.
http://forum.square-enix.com/ffxiv/t...=1#post2066209
but... it eventually came back a couple months later, as shown in this trace here:Quote:
Tracing route to www.google.com [74.125.131.105]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms LPTSRV [10.10.100.1]
2 34 ms 20 ms 26 ms cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 13 ms 12 ms 10 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 27 ms 28 ms 26 ms 24.93.64.124
5 33 ms 35 ms 30 ms 107.14.19.20
6 31 ms 31 ms 30 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.183]
7 29 ms 30 ms 61 ms 74.125.49.181
8 30 ms 46 ms 32 ms 209.85.252.46
9 32 ms 30 ms 30 ms 72.14.236.148
10 41 ms 44 ms 49 ms 72.14.234.168
11 43 ms 45 ms 43 ms 209.85.251.228
12 * * * Request timed out.
13 44 ms 43 ms 43 ms vc-in-f105.1e100.net [74.125.131.105]
Trace complete.
http://forum.square-enix.com/ffxiv/t...=1#post2194801
***note something that changed here---my peering was switched from Cogentco to TATA (as6453). that was done by TWC, because the Cogentco lines had gone to pot on us. SE didn't do that--Time Warner did.Quote:
Tracing route to 199.91.189.25 over a maximum of 30 hops
1 1 ms <1 ms <1 ms LPTSRV [10.10.100.1]
2 49 ms 23 ms 253 ms cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 28 ms 11 ms 15 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 25 ms 26 ms 28 ms xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
5 43 ms 30 ms 32 ms 107.14.19.44
6 31 ms 32 ms 34 ms ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
7 31 ms 31 ms 32 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 71 ms 54 ms 65 ms if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
9 60 ms 55 ms 57 ms 64.86.85.1
10 54 ms 54 ms 57 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
11 53 ms 53 ms 54 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
12 55 ms 64 ms 55 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
13 60 ms 52 ms 54 ms 66.198.96.50
14 55 ms 52 ms 57 ms 192.34.76.2
15 54 ms 57 ms 56 ms 199.91.189.234
16 51 ms 54 ms 56 ms 199.91.189.25
Trace complete.
And then , just a short while later.. it changed again. But this time there were significant changes:
http://forum.square-enix.com/ffxiv/t...=1#post2224866
In case you missed it...aside from the switch back to Cogentco for peering, I also had a new gateway. TWC-SC finally gave up on the failing CMTS. I forget exactly...but I think they had moved me to Hilton Head's gateway at that time (I live in Florence).Quote:
0 G75VXLAP [10.10.100.10]
1 LPTSRV [10.10.100.1]
2 cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
4 24.93.64.134
5 bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
6 107.14.19.99
7 te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
9 be2170.mpd21.dca01.atlas.cogentco.com [154.54.31.106]
10 be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
11 be2108.ccr21.alb02.atlas.cogentco.com [154.54.3.134]
12 be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
13 38.122.42.34
14 10.2.2.1
15 192.34.76.2
16 199.91.189.234
17 199.91.189.25
But... we were far from being out of the woods. While things were generally good, it still had it's WTF moments, like this one here in August:
http://forum.square-enix.com/ffxiv/t...=1#post2359091
Yes... that is right... I was getting shot over to Southern California from South Carolina trying to get to Montreal. It wasn't perfect... but was better than dealing with some downed nodes here on the Eastern Seaboard at the time. Again, Time Warner was making this decision...in an effort to stay ahead of the congested corridors they were finding.Quote:
Tracing route to 199.91.189.30 over a maximum of 30 hops
0 MJ14336 [10.10.100.2]
1 LPTSRV [10.10.100.1]
2 cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 107.14.19.20
7 * ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
8 ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
10 64.86.85.1
11 if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
12 if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
13 if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
14 66.198.96.50
15 192.34.76.2
16 199.91.189.234
17 199.91.189.30
Yes... it's been a long road, and we still weren't there yet---but it was getting progressively better. Eventually, we hit pay-dirt, as demonstrated with the trace in this post in October:
http://forum.square-enix.com/ffxiv/t...=1#post2499951
It still has it's questionable responses...and eventually some of them evened out. They continued to actively monitor the routes for a while. Periodically my modem would reboot and the route would change between Level3, Cogent, and TATA. Sometimes it would change up 2 or 3 times in the same week, sometimes it would be 3 weeks before a change. But it was ALWAYS Time Warner working on my behalf...and always them resolving my problems with the game. The ONLY time we involved SE with the process is when we captured a problem at one of Ormuco's VLAN's, and that was just to include them with the communications to Ormuco about the problem just in case we needed the extra push to get Ormuco to take action in resolving the 250ms+ spikes we had detected at that point in the route after we had cleaned up everything else in between. That issue was handled within a few days and never reared it's head again. Since then, it has ben 100% on Time Warner fixing any issues I have. Most times automatically, but once in a while I would catch the signs first and forward them a snapshot--sometimes it was handled the same night, or if it was the weekend it might take until Monday night when I came home from work before I saw improvement.Quote:
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 37 ms 26 ms 28 ms cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 17 ms 24 ms 29 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 13 ms 16 ms 14 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 28 ms 25 ms 27 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 32 ms 34 ms 35 ms 107.14.19.20
7 33 ms 43 ms 33 ms so-1-1-1.c1.buf00.tbone.rr.com [66.109.1.113]
8 32 ms 31 ms 32 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 62 ms 64 ms 61 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.138]
10 62 ms 76 ms 62 ms if-4-4.tcore2.NYY-New-York.as6453.net [66.198.111.18]
11 59 ms 60 ms 62 ms if-12-6.tcore1.CT8-Chicago.as6453.net [216.6.99.46]
12 58 ms 61 ms 60 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
13 60 ms 69 ms 61 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
14 59 ms 73 ms 61 ms 66.198.96.50
15 62 ms 62 ms 64 ms 192.34.76.2
16 58 ms 59 ms 60 ms 199.91.189.234
17 62 ms 62 ms 59 ms 199.91.189.30
Trace complete.
Barring the few times it was in fact announced to be server side issues by SE, it has ALWAYS been a change in how I was routed that resolved my connectivity/stability issues with the game. And that was ALWAYS handled by going through my ISP's Tier3 support team first--and NOT SE. -
07-29-2015, 08:53 AMAlexikaI thought I was seeing issues there, but it turns out it is just an anti-DDoS feature. Want the MTR I am running right now?Quote:
Originally Posted by Alexika
Code:|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 1 | 1060 | 1058 | 0 | 4 | 473 | 2 |
|lo0-100.PRVDRI-VFTTP-306.verizon-gni.net - 0 | 1068 | 1068 | 4 | 10 | 428 | 6 |
| T0-2-0-9.PRVDRI-LCR-22.verizon-gni.net - 0 | 1068 | 1068 | 4 | 10 | 422 | 8 |
| xe-1-0-8-0.BOS-BB-RTR2.verizon-gni.net - 0 | 1068 | 1068 | 6 | 24 | 428 | 7 |
|xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net - 0 | 1068 | 1068 | 17 | 27 | 461 | 21 |
| 0.ae7.BR1.NYC1.ALTER.NET - 0 | 1068 | 1068 | 15 | 21 | 410 | 17 |
| No response from host - 100 | 213 | 0 | 0 | 0 | 0 | 0 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 1053 | 1049 | 56 | 89 | 652 | 108 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 1052 | 1048 | 56 | 89 | 620 | 270 |
| ORMUCO-COMM.car2.Montreal2.Level3.net - 1 | 1041 | 1034 | 56 | 63 | 534 | 60 |
| 192.34.76.10 - 13 | 719 | 632 | 68 | 78 | 534 | 72 |
| 199.91.189.242 - 15 | 682 | 585 | 0 | 78 | 492 | 74 |
| 199.91.189.33 - 17 | 645 | 539 | 0 | 81 | 503 | 75 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
-
07-29-2015, 09:33 AMRaistO M G.Quote:
Originally Posted by Alexika
It is staring us right in the face. Practically screaming at you.
Even if you want to write off the massive lag spike and lost packets on your local network (which you shouldn't--it is after all the first link in the chain and can affect everything after)...it looks like jitter may be on the high side with Verizon. Then it goes bonkers at Level3.
Based on the data you have presented, you appear to have networking issues that would have an impact on the most perfectly tuned server.
Even if the 600+ spikes were a once-only fluke spike at each of those hops, Level3 is running 56 to 108 with an average of 89 on one hop, and then 56 to 27-0 with an average of 89 at another. That is NOT acceptable. And imagine that... it is LEvel3's car2 hops in Montreal---notorious for being flakey as all get out. They get reported continuously all over the place for a variety of service issues.
Verizon is keeping you on that troubled route. They can take you off of it, just like Time Warner does for me on a regular basis... as demonstrated in the edit I made in my previous post. -
07-29-2015, 09:39 AMAlexikaI fix cars not networks. You might as well speak in Egyptian, because that would mean more to me than anything you just said. Who has networking issues? What kind of issues? How did you determine that? What the heck is jitter? How do I get that fixed? What do I say to the monkey on the phone at Verizon to get them to stop blowing me off?Quote:
Originally Posted by Raist
-
07-29-2015, 09:55 AMRaist
As noted in Blizzard's tracert guide that I keep referring people to, the response times should be tight. There should not be a massive variance between the times at the same hop. That is a big warning sign that something is going bad around that point of the route--could be signalling issue, or over-utilization...congestion is on the rise and their is potential for lost/delayed/retransmitted packets because of it. If you see intermittent * events at one hop, that means you lost packets. Again...often a sign of an overloaded network segment or other technical difficulties are negatively impacting the session. That is part of the problem with using some tools like WinMTR... you aren't able to get a better picture of just where the numbers actually stand. Tracert and ping are the more popular tools--simple, quick snapshots that allow you to better track the numbers to see just what/where the anomalies are rearing their ugly heads.
Basically, you should NOT see a swing of even 50% across the response times at one hop. Granted, depending on what the norm is you can still manage with a high variance, but if it jumps by 100% you are pretty much looking at trouble...and in your example you go beyond even that point.
Think of it like reading your O2 sensor data. If you see the downstream sensor bouncing all over the map from extremely low to extremely high in an erratic fashion...it sets off a red flag for you to take a closer look at your exhaust system and such.
Just for some recent examples, using tracert as described in that blogpost:
This is a trace from the other night when Time Warner, TATA, Level3, Verizon and others were reporting problems in NY/NJ, Atlanta, Ashburn, Nashville, Memphis, and Austin. Things were getting choppy in the game for me, but it was still playable because I am in SC and was only mildly affected by Ashburn, but it was frustrating when you are used to smooth gameplay--for others it was completely debilitating because they were getting a double/triple whammy along the way:
Now look at it tonight, where things are running considerably more smoothly (detected a slight stutter once in a while, but no rubberbanding or big skips):Code:Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms LPTSRV [10.10.100.1]
2 40 ms 13 ms 18 ms cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
3 23 ms 31 ms 33 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 14 ms 15 ms 14 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 26 ms 26 ms 26 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 33 ms 34 ms 90 ms bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
7 31 ms 29 ms 62 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
8 53 ms 48 ms 51 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 133 ms 155 ms 74 ms if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
10 62 ms 62 ms 70 ms 64.86.85.1
11 175 ms 147 ms 173 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
12 66 ms 73 ms 70 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
13 65 ms 75 ms 80 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
14 75 ms 76 ms 78 ms 66.198.96.50
15 79 ms 82 ms 80 ms 192.34.76.2
16 79 ms 78 ms 78 ms 199.91.189.234
17 75 ms 79 ms 78 ms 199.91.189.74
Trace complete.
Code:Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms LPTSRV [10.10.100.1]
2 29 ms 23 ms 24 ms cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
3 25 ms 31 ms 31 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 12 ms 14 ms 15 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 26 ms 26 ms 26 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 31 ms 31 ms 35 ms bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
7 31 ms 30 ms 44 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
8 60 ms 55 ms 72 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 70 ms 74 ms 71 ms if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
10 67 ms 69 ms 67 ms 64.86.85.1
11 71 ms 78 ms 79 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
12 68 ms 75 ms 82 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
13 74 ms 75 ms 72 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
14 77 ms 73 ms 66 ms 66.198.96.50
15 72 ms 69 ms 68 ms 192.34.76.2
16 65 ms 70 ms 70 ms 199.91.189.234
17 58 ms 60 ms 69 ms 199.91.189.74
Trace complete.
-
07-29-2015, 10:04 AMAlexika
They are sending me a new router for tomorrow, but I don't see how that will fix this.
-
07-30-2015, 11:39 PMRover1983What do you mean by those providing the service? As in my own ISP will provide one for me? I need to get this connection issue resolved. Having to use a 3rd party program like PingZapper is fuckin ridiculousQuote:
Originally Posted by Raist
-
07-31-2015, 01:41 AMRaist
The VPN service provider. Pingzapper has their own guides, so does BattlePing, Tunnel Bear, CyberGhost VPN, Hotspot Shield, etc.
As has been stated many times, they usually have a free trial period. But some will have a limited free use policy as well. Tunnel Bear gives you 500MB free every month, and if you promote them on social media you can get an extra 1GB added. Others will limit it by time--like so many hours a day/week/month or something. Some are ad supported (get a pop-up ad periodically, or maybe when you log-on or something weird like that).
The point is, you don't necessarily have to pay for the service to use it in a pinch or for diagnostic purposes. If you find you like how it performs via the VPN and want to use it for more than their free option provides, some of them are actually quite reasonable---like in the neighborhood of $50-$60 for a year of unlimited access. That same Tunnel Bear service I used to prove my point to the TWC tech is only $50 for a year of unlimited use---and it works. Sometimes it fairs better connecting in the states then it does to Canada...but it can and did give better results when I needed to use it.
You may find if you do start using a VPN that you have more uses for it than just the game. I stayed with my free 500MB plan and use it for paying bills and occasionally to stream some content (stupid regional IP blocking). During football season, I prefer to pay them the $7 a month for more VPN access than paying the cable company north of $50 just to watch my games. Just saying....there can be some hidden benefits. -
08-04-2015, 10:41 AMDarkB
Having the same issue over and over, this is getting really frustrating. My ISP is just fine, i play Final fantasy for 9 hours straight, then it just kick me out and get 90k error and 2002. Wont let me back in.
-
09-04-2015, 04:12 PMTheDuxun1977
hi guys i had the same issue error 2002 on my pc for a week lol
so what fixed it was a system restore to before the issue started happening !
hope this help peeps out ! -
09-04-2015, 04:14 PMTheDuxun1977try doing a system restore to a point when you could log in hope that helpsQuote:
Originally Posted by Alexika
-
09-05-2015, 06:30 AMRinSin
Getting 2002 error as well. It played fine until I got a dc, and now can't get into anything. Just stuck on trying to get to lobby or whatever and get the msg lobby connection has encountered an error 2002. Was on cactuar when it happened. Tried a system restore, didn't help.
-
09-05-2015, 06:36 AMNolemTheyve "fixed" Phoenix World and messed up whole EU Data Center with it. We need to wait for those people to fix the whole Data center now. Maybe they crash rest of them at it too.Quote:
Originally Posted by RinSin
-
09-05-2015, 06:39 AMKageSamaDicesame problem
Was queueing for 1+ hour for PvP (FIX THAT TOO???) then error and now continously getting error 2002.
No errors on my side, stable fiber 100/100 line.
Tried iprenew, dnsflush just for the sake of it, pc restart etc.
I am really considering to quit play FFXIV again because it feels like so much is ignored, PvP on one side but server problems are even more unacceptable since I pay to play this game=paying for a service I do not recieve? -
09-05-2015, 06:45 AMNolem
All of us experience the problems. Chaos (EU) Data Center is down apparently.
Also "treathing" to leave the game wont work cause single people are like a small drop in SE sea of people who play this game. They wont even notice few single "units" gone.