HUGE CONNECTION PROBLEM

[Pupugi]

As i've previously posted in threads of this subject from what i gather, the issue here is the "middle men" so to speak, i have been talking with one of devs over reddit about the issue, i've ran multiple tests over varying lengths using winmtr whilst playing and also not playing.

Below is a 4 hour (roughly) trace to the moogle eu server from Slovenia.



As you can see the Frankfurt and Amsterdam hops have a reasonably large spike of a little over 700ms and then the second to last hop has close to 500ms. this trace was left on while i wasnt playing so i cant comment how these spikes felt ingame.

Now, the strange thing about this is that when i did start playing last night, whilest running a tracert i had two tiny spikes whilest in a duty finder (< 1second) then at the end boss a spike which was roughly 3 seconds. the tracert found no problems along the route at this time.


This route was over 20 minutes while inside duty finder.

Now this could be because (probably likely) the instanced content uses different IPs? anyone know of them if that's the case? other than this, i cant see why i had such huge spikes whilst playing and then the tracert to moogle showing nothing.

Secondly, it would be really great if we can all get an official statement on this issue, its obvious this isn't just one or two people, sure its not the majority, but it is pushing people away from coming back, re-subbing and wanting to play.

If anyone would like to know how to use winmtr please let me know, i can write you a short guide so we can get some hard results for the devs to hopefully look into..

Regards

[kwayn]

Same issue on hyperion booted off trying to get to my retainers cant log back on getting 2002 error disconnected from lobby constantly

[Alivya]

Didn't see this one in addressed/reviewing, but I posted as much info as I could in the other one. I can relate the information here as well, but it's so frustrating to be unable to play for a solid 3-4 days.

Edit: unable to play for a whole week now.
And I'm still paying for this.....

I sent in a report today, because it was heinously bad. I was able to get in about three times, but couldn't do anything aside from walk. No menu loads, no chat loads, no message of the day/welcome message at all. The most I got was entering a sanctuary when I finally got into Aleport from where I'd logged off by the Spawning Grounds an entire week ago because I haven't been able to get back in.

[Lawlite5]

Aye, been having the same problem as you, sept I bought the game and got a free month. If this isn't resolved when my trial is up I'm uninstallng and forgetting about it. It causes me too much rage

[Raist]

need to diagnose your route to the servers in Canada. you may very well find there are issues interfering before you even get into Montreal, much less to SE's servers. This is an issue your ISP needs to address--either by revisiting their peering agreement with the Tier1 they are using to get you into/across Canada, or switching you to use one of their other partners to get you there.

this has been gone over repeatedly on these forums... and for the most part those that have run the traces to the proper servers have found this to be true. Lately, Level3 has been flagged for having the most problems... but it is a moving target, so the offending party changes periodically. It's nothing new... it's been going on for well over a decade. Briefs have been filed repeatedly with the regulatory commissions to try to enforce fair practices amongst the peering partners (most recently it was TATA and Level3 going after the big ISP's like TWC, Comcast, Verizon, etc.). But they've made little to no headway on their end, so it basically falls back to those of us that pay the ISP's to push them to clean up their act.

If you find signs of high congestion/packet loss issues in your traces, forward them to your ISP's Tier3 support. They are the ones that have to escalate this, not the Tier 1/2 guys that answer the phone or come check your local cables or even the localized node. These issues are frequently rooted deep into our routes, and it takes a higher level department to resolve it. Your ISP CAN and NEEDS to resolve it. They have the power to clean up your route one way or another... just need to hold them accountable to do it. After all, a large portion of your ridiculous internet fees pay for the customer service department and it's payroll.

[Retnaburn]

This has NOTHING to do with our ISP. I've had this problem for months. I lived in Minnesota using Comcast. I recently moved in with 3 other people that all play the game and do not have the problem. I now live 5 hours away and use a different ISP, Time Warner, and still have the problem. NONE of the THREE other people that I live with have this problem.


This is an account bound problem.

[Kaaylryn]

I don't know if this is account bound, or server, or ISP hops. I do know that after every or every other numbered patch, I suffer 90K issues followed by lobby errors. This will go on for a day to a week and then mysteriously fix itself.

This has been a repeating issue since launch and SE can't seem to stabilize their connections before this starts happening. I would gladly wait an addition 2 or 3 hours on patch day for them to wave a magic wand or sprinkle fairy dust so that no one has to be subjected to this most annoying problem. It has been a year after all.

[bigpoppa]

When Patch 2.35 went live, I got disconnected via Error 90000 about every 5-10min. And now ever since the hotfix/maintenance, my disconnects have actually INCREASED in frequency to about every 2min. WTChocobo?!?!

[Scornful_Egotist]

Yep.

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 Deaf-Mute-PC [10.0.0.14]
1 10.0.0.1
2 67.161.176.1
3 xe-7-1-2-32767-sur03.sacramento.ca.ccal.comcast.net [68.87.221.193]
4 162-151-18-133-static.hfc.comcastbusiness.net [162.151.18.133]
5 he-3-5-0-0-11-cr01.sanjose.ca.ibone.comcast.net [68.86.92.181]
6 pos-0-4-0-0-pe01.529bryant.ca.ibone.comcast.net [68.86.87.146]
7 ix-0-1-1-0.tcore1.PDI-Palo-Alto.as6453.net [66.198.127.33]
8 if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.127.2]
9 if-11-3.tcore2.CT8-Chicago.as6453.net [66.198.144.58]
10 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
11 66.198.96.58
12 te7-3.dr9.mtl.iweb.com [67.205.127.214]
13 72.55.128.44
14 184.107.107.176

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Deaf-Mute-PC [10.0.0.14]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 67.161.176.1
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% xe-7-1-2-32767-sur03.sacramento.ca
.ccal.comcast.net [68.87.221.193]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% 162-151-18-133-static.hfc.comcastb
usiness.net [162.151.18.133]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% he-3-5-0-0-11-cr01.sanjose.ca.ibon
e.comcast.net [68.86.92.181]
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% pos-0-4-0-0-pe01.529bryant.ca.ibon
e.comcast.net [68.86.87.146]
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% ix-0-1-1-0.tcore1.PDI-Palo-Alto.as
6453.net [66.198.127.33]
0/ 100 = 0% |
8 17ms 0/ 100 = 0% 0/ 100 = 0% if-2-2.tcore2.PDI-Palo-Alto.as6453
.net [66.198.127.2]
0/ 100 = 0% |
9 67ms 0/ 100 = 0% 0/ 100 = 0% if-11-3.tcore2.CT8-Chicago.as6453.
net [66.198.144.58]
0/ 100 = 0% |
10 90ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.45]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 66.198.96.58
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% te7-3.dr9.mtl.iweb.com [67.205.127
.214]
0/ 100 = 0% |
13 89ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
14 90ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

[Raist]

Yep.

Tracing route to 184.107.107.176 over a maximum of 30 hops

As detailed earlier in the thread, that IP is NOT tied into the game. Need to be using the IP your client actually uses (or at least your actual lobby server) so that you are hitting a route to Ormuco (SE's ISP) and then a server actually used by the game. The Canadian IP's start with 199, and most of the Japan ones will start with 124.

TATA started having issues last night as well as the ongoing problems with Level3. TWC switched me back to Cogent lines via Atlanta, and my connection is once again stable.

Hate to keep beating the dead horse.... but once again proof that there IS something your ISP in fact can do about the issue when it is found to be in route to Ormuco.