Is it my ISP or some other problem?

[DragoonChampion7]

Ok, so I know I don't have the greatest ISP, Time Warner Cable, but I've been able to play FFXIV since August2013, with the occasional disconnect once in awhile. However the last month, maybe 2 months already, Its been really bad. Yesterday I was logged in for about an hour before I was disconnected. Sometimes it's so bad that I get disconnected every 5 minutes or when I get disconnected and try to go back in, in a matter of seconds, get kicked out again. The reason I ask if it is really my ISP is because when I do Coil, I'm on Skype with my FC. I would get disconnected from FFXIV but still be on Skype talking to them. Also, I have tried resetting my internet, problem still occurs. I've called them up and they would reset my internet from where they were. I've also had two modems already replaced by my ISP. So is it my ISP or is this a problem with FFXIV itself?
I'm sorry if these sound like silly questions but i'm a nub when it comes to these things.

Also, what is the difference between the 90000 Error and the 90002 Error? I get both.

[Kerberon]

Ok I'm going to have you use a computer for this, if you're on a ps3/4 you'll need to use your pc from the same connection that your playstation uses.
Open a cmd prompt.
Type pathping ipaddress

Replace the above ipaddress with the correct address from here.
North America Datacentre | square-enix.montreal.com | IP address: 184.107.107.176

Europe Datacentre | eu.square-enix.com | IP address: 209.130.141.243

Japan Datacentre | jp.square-enix.com | IP address : 202.67.53.202

Post your results here and we can get a better idea of if it's you or the servers.

[DragoonChampion7]

I hope you can explain what this means cuz I sure don't know what this means.

10 29ms 4/ 100 = 4% 3/ 100 = 3% if-5-5.tcore1.NYY-New-York.as6453.net [216.6.90.5]
0/ 100 = 0% |
11 31ms 1/ 100 = 1% 0/ 100 = 0% if-11-2.tcore2.NYY-New-York.as6453.net [216.6.99.1]
0/ 100 = 0% |
12 37ms 2/ 100 = 2% 1/ 100 = 1% if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
0/ 100 = 0% |
13 35ms 2/ 100 = 2% 1/ 100 = 1% if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
0/ 100 = 0% |
14 43ms 1/ 100 = 1% 0/ 100 = 0% 64.86.31.42
1/ 100 = 1% |
15 --- 100/ 100 =100% 98/ 100 = 98% ae31.cr6.mtl.iweb.com [184.107.1.254]
0/ 100 = 0% |
16 --- 100/ 100 =100% 98/ 100 = 98% te8-4.dr10.mtl.iweb.com [67.205.127.82]
0/ 100 = 0% |

[Kerberon]

I hope you can explain what this means cuz I sure don't know what this means.

10 29ms 4/ 100 = 4% 3/ 100 = 3% if-5-5.tcore1.NYY-New-York.as6453.net [216.6.90.5]
0/ 100 = 0% |
11 31ms 1/ 100 = 1% 0/ 100 = 0% if-11-2.tcore2.NYY-New-York.as6453.net [216.6.99.1]
0/ 100 = 0% |
12 37ms 2/ 100 = 2% 1/ 100 = 1% if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.30]
0/ 100 = 0% |
13 35ms 2/ 100 = 2% 1/ 100 = 1% if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
0/ 100 = 0% |
14 43ms 1/ 100 = 1% 0/ 100 = 0% 64.86.31.42
1/ 100 = 1% |
15 --- 100/ 100 =100% 98/ 100 = 98% ae31.cr6.mtl.iweb.com [184.107.1.254]
0/ 100 = 0% |
16 --- 100/ 100 =100% 98/ 100 = 98% te8-4.dr10.mtl.iweb.com [67.205.127.82]
0/ 100 = 0% |

ignoring hops 15 and 16 where you finally hit iweb where the servers are because they always give odd numbers due to their configurations, your problem is your connection. Each of those % numbers stands for your loss at each leg of the trip. You are getting a few % of loss on each hop which frankly is what's likely giving you problems. You should have 0% the whole way down.

[DragoonChampion7]

Thank you. This just means that I still must do battle with TWC. lol

At least now I know its not some other issue.

[Poki]

You can try logging into your cable modem by going to http://192.168.100.1 and look at the signal reading page.

downstream power levels should be between -10 to +10 dbmv, with signal to noise above 32 db

upstream power level should be between 35-52 dbmv

Also check if there are a large number of uncorrectable errors/bits/codewords in relation to the total bits/codewords passed (and refresh the page to see if the uncorrectables keep climbing higher)

If any of these are out of range, then TWC needs to have a technician visit you and adjust the signal and/or check your cable lines for interference/ingress

[Raist]

I'm also a TWC customer (SC, get routed up through Raleigh or Charlotte, depending on what they are doing to try to fix my issues... periodically I'll also get shot down to Atlanta).

Just wanted to encourage you to go after TWC with your issues, but wanted to make sure you had better information when you contact them. Some of us have leaned really hard on our ISP's about such issues in the past as well as now, and with good, detailed information you actually can make some headway. We managed to get escalation to investigate an issue with our headend that was only providing 6 downstream channels instead of 8, which was a MAJOR point of congestion for an entire region of residential customers in/around Florence. Just confirmed it tonight with my Zoom 8X4 modem that all 8 channels are now working again. Took 3 months of sticking it to them... but we eventually got it addressed. We also got them to put a fire under the collective arses of TATA, Cogent, and Level3 to address some routing issues we spotted coming through the east coast corridors, so we now can get a solid 70ms or less latency throughout the route--except for a primetime issue with our main CPE, it's the best it's ever been for this game and several other web services like Netflix, Hulu, etc.

Those IP's you were given are a good "test for smoke" approach, but may not ultimately get you the resolution you need. Those IP's are NOT the data centers for XIV. They are websites hosted on servers in a different location, and run off a different ISP's backbone. Our problems are with reliably getting to servers hosted on Ormuco lines, and not i-web. That may seem trivial because they are both in Montreal, but in the mess that is the internet, a difference of just a few blocks distance between two points can mean a world of difference depending on how the routing data is managed. In the case of TWC, it is FUBAR beyond belief, and some of their routing partners are just as bad if not worse. I have seen my routing shoot out to Missouri, up to Chicago then back (NSA scan, YAY!), then all the way out to LA, Up to Seattle, around British Columbia, across to Toronto, and then FINALLY to Montreal. I live in Florence, SC...which actually has a major fiber trunk that runs from Columbia to Myrtle Beach, major segments through NC, VA/DC, etc. on up to Montreal... so such outlandish routing errors should NOT be occurring from my point of origin. There are FAR better routes along the EAST COAST for me to take--or even the Midwest for that matter. I should NEVER have to go to Southern California, up through Washington, then around BC and back across Canada to get to Montreal. But, nevertheless... it can and DOES happen because of shoddy pathing on the part of either TWC or their routing partners. This kind of crap goes on all the time with TWC, and we have been giving them h3ll about it for some time trying to get such errors resolved. You can see lots of conversations about it over at the TWC forums.

Anywho... when you contact Time Warner (or anyone else contacting their ISP for that matter), you need to push for one very specific thing. Just how you get there may differ, as many have these @#$@#$ automated menus you have to wade through before you talk to a live person... power cycle this, power cycle that, reset your TCP/IP settings and flush DNS... all that BS that usually has absolutely NOTHING to do with your problem because it often resides upstream, typically in another state or possibly even another COUNTRY for that matter (and yes, it has left a bitter taste in my mouth over the years).

What you need is Tier3 support. PERIOD.

Accept NOTHING LESS for addressing your problem. These are the guys who actually know wtf a tracert can be used for, and actually may stand a chance of isolating your problem and getting the proper people involved in researching and <hopefully> fixing your problems. If they balk at you, ask for a supervisor... ask for escalation... whatever it takes to get to someone of higher authority until you find someone that gives you a means to send them some data about your connection problems. In most cases, you don't need to keep resetting local hardware or keep waiting for technicians to come verify your wiring is OK.

Those repeated on-site visits are really only necessary if a signalling issue is suspected locally---and this can usually be gleaned from the modem's logs and signal pages, which you have access to yourself as noted earlier. Print them out when you see a wide variance in the signal stats. Make sure to get snapshots of both "good" and "bad" states--copy/paste them into a document (or generate a PDF if you can) as well in case you want to forward them via email later. Make sure to get your log file as well, as it may provide more insight into whether fluctuating signal levels are impacting you enough to be causing your problems. There are sites out there to help you "print" a page to a PDF file (PDF995 has a cool tool you can install that does it--if you've used H&R Block Tax software in recent years, it's installed on your printers list). These reports can be very useful for narrowing down if there is a problem locally (like your wires or your modem itself), somewhere out on the poles, or deeper into their CMTS.

Secondly, you need to provide useful information about the games actual connections so they can follow the specific path(s) you are getting routed along to help them pinpoint where the problems are occurring. The tracert is a phenomenal report to that end--but you need to be hitting a proper IP so it shows the actual routing you are being assigned according to the registered geolocation of both your point of origin and the intended destination IP(s). On Win7/Win8 machines, it's pretty simple to do, as you can see what IP's the FFXIV is connecting to with Resource Monitor's TCP and/or Networking sections (run resmon.exe from your start/search box).

Unfortunately you don't have such simplicity on the consoles. We are, however in luck because so many people have been investigating this issue for a REALLY long time, so we know a lot of the IP's actually being used. There are also DNS names for servers embedded in the executables that can be used for testing DNS data as well. So, without further ado and more rambling from me, I will paste a list of some known DNS names and their currently resolving IP addresses, followed by some additional IP's I have noted for mine and other people's world and lobby servers. You can include some of this info with your communication with Tier3 (or higher if you get really lucky) so they can do more testing on their own.

***note that the servers in Montreal begin with 199, servers in Tokyo begin with 124. This is important because the client is in communication with BOTH countries for various tasks***

frontier.ffxiv.com 124.150.157.190
patch-gamever.ffxiv.com 124.150.157.126
neolobby01.ffxiv.com 124.150.157.158
neolobby02.ffxiv.com 199.91.189.74
neolobby03.ffxiv.com 124.150.157.157
neolobby04.ffxiv.com 199.91.189.93
neolobby05.ffxiv.com 124.150.157.156
neolobby06.ffxiv.com 199.91.189.94
secure.square-enix.com 124.150.158.110

199.91.189.74
199.91.189.60
199.91.189.38
199.91.189.36
199.91.189.31
199.91.189.25
(basically, a lot of IP's in this subnet--all of them used by the servers in Canada for the NA/EU subscriptions)

Patches appear to have been delivered via Akamai at times? A few particular IP's seem to come up routinely:
24.143.200.227
24.143.200.234
24.143.200.241

Several SE IP's in Japan routinely show up during activity requiring authentication (login and such), and may prove useful if issues are routinely during sign-on to both the mogstation and the game, as well as changing zones in the game:
124.150.158.110
124.150.158.117
124.150.157.126
124.150.157.190
(Again, there is a BIG subnet here owned by SE. And yes, that is both 157 and 158 in the 3rd octet. Some of the IP's in this group have been seen in use with other games in the past)