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

[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?

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.

[Erdrick_Alefgard]

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).

[Erdrick_Alefgard]

Bump. Please see response from RCN.

[Laevantine]

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.

[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

tried again and got this at hop 11:

44ms * * 199.91.189.234

I dont know what each time means.

[Erdrick_Alefgard]

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.

[Mostaru]

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

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.

[No_Skilz]

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

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

[suncrashesdown]

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

[Miburo]

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