Lag spike/90000 error DC victims -- Help gather data on the problem

Okay. So as I've pointed out in a couple threads I've posted on, I think I have an idea what the deal is? But I don't have many data points, and so I could use your help -- hopefully if my theory is right we can make the tech support folks take notice?

Here is what you can do to help:

1. Run a traceroute to "neolobby02.ffxiv.com" -- if you don't know how to do this:

• Windows: Accessories > Command Prompt > tracert neolobby02.ffxiv.com
• Mac: Terminal > traceroute neolobby02.ffxiv.com
• Linux: If you're a linux user I can't imagine you don't know how to traceroute!

2. Check the output for a line mentioning "tiscali.NET" -- if you're an RCN customer like me, it's probably the first hop after you stop getting RCN hops.

3. If you find a "tiscali.NET" hop in your trace, AND you're getting the lag spikes/rubberbanding/90k DCs, can you post here affirming that fact?

Now, caveat: I'm not a network tech. I don't REALLY know that this is what's going on. But every time I connect to the NA/EU data center, I check my route and ping, while watching the game, and every time I lag out/DC, it's because my connection stopped at the tiscali.NET hop.

Anyhow, scientific method, right? Gather data, draw conclusions. Hopefully if we find something useful we can take that to tech support and get this resolved soon.

Been there done that. It stops on two of the hops. Here is the response from RCN after days of contacting them:

"I apologize but at this time there is no ETA being provided. The problem is between ORMUCO-WebHost) and ONAM. A provider issue.

Thanks you for your understanding in this matter. We are working with the providers to resolve the issue as quickly as possible."

While FFXIV's GAME SERVER is not directly at fault, their horrendous hosting service, likely in a co-lo (a server farm in a remote location, saving costs) is at fault. They pay those fools pennies on the dollar to host their services, so they need to be on top of this. Instead, they are going about it as though it's a tiny issue, completely avoiding the fact that thousands upon thousands of players are having this issue.

FYI - My two failing hops are equinox-was12.ip.tiscali.net(206.126.236.19 and is the MAIN culprit) and xe-1-0-0.mtl10.ip4.tinet.net(89.149.185.41 and it sometimes fails albeit not nearly as often as the other hop).

Bump. Please see response from RCN.

Quote:

---

Originally Posted by Erdrick_Alefgard

FYI - My two failing hops are equinox-was12.ip.tiscali.net(206.126.236.19 and is the MAIN culprit) and xe-1-0-0.mtl10.ip4.tinet.net(89.149.185.41 and it sometimes fails albeit not nearly as often as the other hop).

---

YUP. Me too. Hence this thread! Hoping if a whole bunch of us pop up mentioning this, it might get noticed? I mean, I doubt it, but I live in hope.

Yes I am an an RCN customer. Yes tiscali.net is in the tracert. yes i have bad lag spikes and random 90k's. Only questionable hop was hop 11. Shows this:

* * 41ms 199.91.189.234

tried again and got this at hop 11:

44ms * * 199.91.189.234

I dont know what each time means.

Quote:

---

Originally Posted by No_Skilz

Yes I am an an RCN customer. Yes tiscali.net is in the tracert. yes i have bad lag spikes and random 90k's. Only questionable hop was hop 11. Shows this:

* * 41ms 199.91.189.234

I dont know what each time means.

---

It sends three ping requests on each hop. The asterisks imply the ping request timed out. In your case, you got two that timed out, and one that replied in 41ms (.041 seconds) for a packet loss rate of 66%. One of your other hops was likely at fault when that occurred.

I'm using RCN as well, I got huge lag spikes and very frequent error 90000

I'm not sure how to read this thing, but here is the log

Quote:

---

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 6 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 8 ms bdl1.wsd-ubr1.qens-wsd.ny.cable.rcn.net [10.19.1
84.1]
3 8 ms 13 ms 11 ms bvi4.aggr1.nyw.ny.rcn.net [208.59.246.2]
4 20 ms 21 ms 22 ms tge0-1-0-0.core2.nyw.ny.rcn.net [207.172.15.89]

5 21 ms 20 ms 22 ms tge0-0-0-2.core2.phdl.pa.rcn.net [207.172.19.228
]
6 18 ms 19 ms 19 ms tge0-0-0-2.core2.lnh.md.rcn.net [207.172.19.11]

7 18 ms 18 ms 17 ms tge0-0-0-6.border1.eqnx.va.rcn.net [207.172.19.9
]
8 21 ms 20 ms 22 ms equinix-was12.ip.tiscali.NET [206.126.236.19]
9 42 ms 42 ms 82 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
10 41 ms 41 ms 41 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
11 44 ms 47 ms 43 ms 192.34.76.2
12 42 ms 44 ms 44 ms 199.91.189.234
13 47 ms 42 ms 42 ms 199.91.189.74

Trace complete.

---

Ran tracert again and request timed out where tiscali.net usually is.

Quote:

---

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.x.x
2 8 ms 8 ms 17 ms bdl1.drf-ubr1.atw-drf.pa.cable.rcn.net [10.19.0.
1]
3 8 ms 23 ms 8 ms bvi4.aggr1.atw.pa.rcn.net [209.122.64.34]
4 19 ms 21 ms 26 ms tge0-1-0-7.core2.phdl.pa.rcn.net [207.172.19.130
]
5 20 ms 32 ms 18 ms tge0-0-0-2.core2.lnh.md.rcn.net [207.172.19.11]

6 19 ms 19 ms 20 ms tge0-1-0-7.border1.eqnx.va.rcn.net [207.172.19.2
05]
7 * * * Request timed out.
8 39 ms 50 ms 40 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 41 ms 43 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 41 ms 43 ms 42 ms 192.34.76.2
11 41 ms 67 ms 42 ms 199.91.189.234
12 41 ms 40 ms 43 ms 199.91.189.74

Trace complete

---

Starting from the RCN hops...

3 bvi80.aggr2.chgo.il.rcn.net (207.229.191.131) 14.823 ms 16.452 ms 16.046 ms
4 bdle2.border1.eqnx.il.rcn.net (207.172.15.196) 16.653 ms
bdle3.border1.eqnx.il.rcn.net (207.172.15.212) 18.715 ms 17.426 ms
5 ibx-chi.ip.tiscali.net (206.223.119.19) 17.778 ms 17.932 ms 18.176 ms
6 * * xe-1-0-0.mtl10.ip4.tinet.net (89.149.185.41) 66.693 ms
7 ormuco-gw.ip4.tinet.net (216.221.156.110) 61.499 ms 61.941 ms 61.420 ms
8 192.34.76.2 (192.34.76.2) 101.793 ms 51.360 ms 51.544 ms

Bro-tier ISP RCN trying to get SE to make our game work. Address this stuff already, SE. It's getting ridiculous.

So came here because this EXACT same problem. Guess what? I have RCN too! -_-

This is really getting out of hand. I do have a question though, are you all experiencing this problem after the Sep. 3rd server/maintenance? I ran the game perfect prior to that maintenance.

I called RCN thinking it was something with my service, and went out and replace my modem and ofc I'm still having this problem. I’m not sure whats going on in this log but here ya go :P

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 13 ms 13 ms bvi200.aggr2.sbo.ma.rcn.net [10.65.92.101]
4 26 ms 27 ms 30 ms tge0-0-0-0.core1.sbo.ma.rcn.net [207.172.15.131]

5 25 ms 24 ms 25 ms tge0-0-0-1.core1.nyw.ny.rcn.net [207.172.19.219]

6 21 ms 20 ms 21 ms tge0-1-0-2.core1.phdl.pa.rcn.net [207.172.19.216

7 25 ms 25 ms 25 ms tge0-0-0-2.core1.lnh.md.rcn.net [207.172.19.227]

8 23 ms 31 ms 25 ms tge0-1-0-6.border1.eqnx.va.rcn.net [207.172.19.7

9 22 ms 32 ms 22 ms equinix-was12.ip.tiscali.NET [206.126.236.19]
10 44 ms 101 ms 51 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
11 49 ms 47 ms 47 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 44 ms 46 ms 46 ms 192.34.76.2
13 45 ms 42 ms 43 ms 199.91.189.234
14 44 ms 43 ms 44 ms 199.91.189.74

Yeah, most people experiencing this problem seem to have had it starting around Sept. 2nd/3rd. There were people with RCN, Verizon Fios, an ISP in japan, and somewhere else posting in the same thread. My game was also working completely fine prior.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 8 ms 7 ms 7 ms 10.210.128.1
3 8 ms 7 ms 7 ms gig1-0-0.1105.wlmgncilm-rtr1.ec.rr.com [24.25.32
.76]
4 17 ms 15 ms 15 ms 24.93.64.18
5 23 ms 23 ms 23 ms 107.14.19.42
6 20 ms 19 ms 22 ms ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
7 19 ms 19 ms 22 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.
149]
8 * 32 ms 33 ms if-11-2.tcore2.NJY-Newark.as6453.net [216.6.87.1
38]
9 32 ms 32 ms 46 ms if-4-4.tcore2.NYY-NewYork.as6453.net [66.198.111
.18]
10 36 ms 35 ms 47 ms if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226
.13]
11 79 ms 35 ms 32 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
12 32 ms 36 ms 33 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
13 32 ms 33 ms 33 ms 66.198.96.50
14 32 ms 32 ms 32 ms 192.34.76.2
15 33 ms 33 ms 36 ms 199.91.189.234
16 33 ms 32 ms 33 ms 199.91.189.74

Trace complete.

Dunno what this is, but here ya go. My ISP is Roadrunner.

Quote:

---

Originally Posted by Spizzzel

This is really getting out of hand. I do have a question though, are you all experiencing this problem after the Sep. 3rd server/maintenance? I ran the game perfect prior to that maintenance.

---

Yeah, I did too. It started on Monday morning before the maintenance, but then the 1017s were so thick it was irrelevant. After the maintenance, problem persisted.

Quote:

---

Originally Posted by Spizzzel

9 22 ms 32 ms 22 ms equinix-was12.ip.tiscali.NET [206.126.236.19]

---

And there's the problem child server, right on schedule.

So is this a RCN issue or a SE new server issue? If its a RCN issue i will switch idc, I've been thinking about switching for awhile. Thing is it seems like a lot of people are having this issue even with other isps...

Quote:

---

Originally Posted by Spizzzel

So is this a RCN issue or a SE new server issue? If its a RCN issue i will switch idc, I've been thinking about switching for awhile. Thing is it seems like a lot of people are having this issue even with other isps...

---

I don't think it's an RCN issue. I think it's an upstream issue... as someone said earlier in the thread, it's probably Square's co-location service for the NA/EU data center.

Quote:

---

Originally Posted by Spizzzel

So is this a RCN issue or a SE new server issue? If its a RCN issue i will switch idc, I've been thinking about switching for awhile. Thing is it seems like a lot of people are having this issue even with other isps...

---

RCN says they are aware of the issue, but it's not a problem on their hand. Plus there are a ton of people with many different services reporting on the issue.

I'm in NYC (EST zone) and on Behemoth. Here's what I found:

home: RCN - 20/3Mb, 20ms ping - I get 90k error many times withing an hour, disconnect and giant lag spikes.
my office: 3rd Gear - 100Mb up/down, 5m ping - I get 90k errors many times, giant lag spikes, same issues
over VPN to client one: NYIC - 100Mb up/down, 10ms ping - perfect

So now I'm actually using my clients VPN to play this game. It's not perfect but I don't get disconnected/lagspikes/90k

I suggest trying VPN connections if you have access. This might actually be ISP related which promises to be a giant issue. Yet we didn't have this before the "fixes".

Having the same issue since they did the server upgrades and all that wednesday. Had no issues before other than the world is full mess everyone else had. Now it's easier to log in but I can only play 5-20 minutes before the 90k pops and then its a 5-15 minute wait for the server to boot me off after the disconnect.

As of yesterday, a bunch of similar threads with 10+ pages of responses were locked and moved to the "Resolved Issues" section. While we know they aren't resolved as I am having the same problem, I believe a dev posted at the end of each of them that they are looking into it. According to them, the threads were locked and moved because it was an issue that could not be resolved via the forums.

See:
http://forum.square-enix.com/ffxiv/t...thread./page12
http://forum.square-enix.com/ffxiv/t...-issues/page14

Bumping, again, until I see something on the Final Fantasy 14 website about this issue. Your lackluster and mostly lacking altogether responses do not instill faith that his problem is being taken seriously. Your game is absolutely awesome. Take it as a complement that we still want to play after this sadomasochistic relationship you've established with your players. RESPECT US AND GIVE A VALID RESPONSE OR THE BUMPS AND NEW THREADS WILL CONTINUE TO COME.

Quote:

---

Originally Posted by TheMathmagician

As of yesterday, a bunch of similar threads with 10+ pages of responses were locked and moved to the "Resolved Issues" section. While we know they aren't resolved as I am having the same problem, I believe a dev posted at the end of each of them that they are looking into it. According to them, the threads were locked and moved because it was an issue that could not be resolved via the forums.

See:
http://forum.square-enix.com/ffxiv/t...thread./page12
http://forum.square-enix.com/ffxiv/t...-issues/page14

---

Issue cannot be resolved via forums ? do we have another choice ? .... open a ticket ? lol

Bump. Still getting frequent lag and error 90000 disconnects.

was already a thread like this, they locked it and put it in resolved.
NOT Being Addressed/Currently Reviewing
but resolved.
It is not resolved.
Good luck, appears they don't care.

I'm not having lag spikes or dc issues but I have not been able to log on all day. I get error 2002 and if I can actually get to character selection I get error 90000. I know this is a bit off your topic but since this is the only thread I saw that was even remotely close I figured I would look at it. I tried traceroute and for the first 14 hops I get "request timed out". So do you think this would be an internet issue?

http://forum.square-enix.com/ffxiv/t...s-issues/page6

this thread had a lot of info in it. VPN seems to work so far from me. but it's still unacceptable that I have to go that far to play a game I paid for.

Someone in the Japanese forums started a thread and I posted in it as well. If this isn't resolved soon, I plan to call Japanese customer support myself. I suggest anyone with Japanese language ability do the same. Here's the thread:

http://forum.square-enix.com/ffxiv/t...83%84%E5%85%89

Bump. Game is unplayable at the moment thanks to constant error 90000.

Quote:

---

Originally Posted by Laevantine

Okay. So as I've pointed out in a couple threads I've posted on, I think I have an idea what the deal is? But I don't have many data points, and so I could use your help -- hopefully if my theory is right we can make the tech support folks take notice?

3. If you find a "tiscali.NET" hop in your trace, AND you're getting the lag spikes/rubberbanding/90k DCs, can you post here affirming that fact?

---

Yes and Yes

Quote:

---

Originally Posted by Shawnji

Someone in the Japanese forums started a thread and I posted in it as well. If this isn't resolved soon, I plan to call Japanese customer support myself. I suggest anyone with Japanese language ability do the same. Here's the thread:

http://forum.square-enix.com/ffxiv/t...83%84%E5%85%89

---

I don't know japanese, but I think it's a good idea to post over there since we're getting no response here. Better chance of the problem getting noticed, at least.

I just posted something really basic to hopefully get the point across that this is happening and it needs their attention.

Bump again.

Quote:

---

Originally Posted by Melodius

was already a thread like this, they locked it and put it in resolved.
NOT Being Addressed/Currently Reviewing
but resolved.
It is not resolved.
Good luck, appears they don't care.

---

I think it's the fact that they know it's an issue with the servers and that it's out of our hands to be able to fix if ofc so there is no point in going into it more via forum help requests. ALTHOUGH, if thats the case and they are actually moving towards a fix, they should come out and straight up acknowledge the problem to put our minds to ease.

Quote:

---

Originally Posted by SoulBlue

Issue cannot be resolved via forums ? do we have another choice ? .... open a ticket ? lol

---

LOl, you can try. They answered mine but they addressed a different past issue with the game that was resolved that had nothing to do with the ticket I made for this error.

bump for relevance

All they have to do is move them to Being Addressed/Currently Reviewing and post saying it is being worked on and there will be a emergency maintenance as soon as we locate the issue... HOW HARD IS THAT.

Because a dozen of you will be in here making threads "HOLY SH!T IT'S BEEN 12-1/2 MINUTES SINCE YOU SAID YOU WERE WORKING ON THE PROBLEM WHEN WILL I BE ABLE TO LOGIN?!?!?!"

Confirming that I am also having the lag spike issues with occasional 90000 crashes.

My ISP is RCN-Chicago and I also have ibx-chi.ip.tiscali.NET in my tracert.

hmms yet when others couldn't login there was a update on launcher or forums...

Eh, I think there would be a lot of people that would be grateful for even that though. Yes, we all wish we could play a perfect game, but knowing that they are aware and actively looking for a fix would put a lot of minds to ease.

It's not only with the hew servers, i started my first toon on Ultros and i get the same erreur then on the new one on Lamia. Keep getting booted btw 5-20min max. Can be in town or field or dungeons it doesnt matter. My friend who is using same compagny (videotron) doesnt have any problem staying in game on Lamia server.