HUGE CONNECTION PROBLEM

[Raist]

I'm getting the exact same problem, and i'm from Canada

It's less of an issue over where you start, but more of how you get there.

The internet sort of gets routed like the mail--you can get sloughed off to another city just to deliver something right next door. But it's much worse, you can get routed off to another state or province just to connect to a server that is physically at the end of your street.

Try running a trace to one of the lobby servers... you may find you bounce around quite a bit--and each hope is a potential point of failure on the way both there and back:

neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com
(these are the CA ones... the JP ones have odd numbers assigned)

[yagyujubei]

Throwing in my hat. it's a 90k fest every time I try to do anything in the game. this is like release day lag >_>.

[Kassatsu]

I've been having lag issues since 2.35 patch always between 7pm-12am est and 2.4 has just made it worse. Made a ton of post various thread and nothings been done about it so I doubt they care enough to bother. Most of my FC has been having the same issues.

[Lemage]

It's all fine and well to have problems with your servers, but when it happens this often that people already know where to go and where to look to report the issue within seconds then yeah, no, it's a bad thing. I reported the problem in game 10 mins ago and regardless of the fact that it's on here as currently under review, they still had the nerve to tell me it "looks like it's my isp" okay, I'll play along I thought. so, I tethered to my phone's 4G. a different isp, we'll call them IsP B. B had the exact same issue as A. decided screw it, I'll go the extra mile just to spite them for ignoring an issue that's obviously not one isp or one country. Asked my neighbour if i could connect to their net for 15 minutes their isp is yet ANOTHER one. IsP C. C had all the problems of B and A. so if it really is just A that's the issue, then explain what in the hell is going on with B and C?! This same stuff happens all too often on a game that's wellllll past launch.




EDIT: just to add, I'm from Australia.
isp's | A: Telstra Adsl2+ | B: Optus 4G | C: Vodafone Mobile 4G on a Router |

[Raist]

It's all fine and well to have problems with your servers, but when it happens this often that people already know where to go and where to look to report the issue within seconds then yeah, no, it's a bad thing. I reported the problem in game 10 mins ago and regardless of the fact that it's on here as currently under review, they still had the nerve to tell me it "looks like it's my isp" okay, I'll play along I thought. so, I tethered to my phone's 4G. a different isp, we'll call them IsP B. B had the exact same issue as A. decided screw it, I'll go the extra mile just to spite them for ignoring an issue that's obviously not one isp or one country. Asked my neighbour if i could connect to their net for 15 minutes their isp is yet ANOTHER one. IsP C. C had all the problems of B and A. so if it really is just A that's the issue, then explain what in the hell is going on with B and C?! This same stuff happens all too often on a game that's wellllll past launch.




EDIT: just to add, I'm from Australia.
isp's | A: Telstra Adsl2+ | B: Optus 4G | C: Vodafone Mobile 4G on a Router |

Could simply be something going on along the "Southern Cross" transit to the states (coming in through Southern California or Seattle--known to act up from time to time). Or, you may get lucky and get through the west coast fine, only to get hammered elsewhere in route--anywhere between Vancouver and Montreal or across theMmidwest, SouthWest, North East corridors... you may be able to figure it out with some traces, and then you'll have something in hand you can forward to the Tier3 guys to investigate matters for you.

Ran a few google searches real quick hoping to find a good visual, but couldn't find a current one to run as an image in the post. Got some links to interactive maps and articles with graphics and such... but only an older image for Vodaphone. But it kinda shows the paths you are taking to get to North America to hopefully put it in better perspective. With the limited paths you have at certain points along the route, it greatly increases your chances of having issues in route. May need to lean hard on them to put pressure on their partners if you can. IDK if you guys have the consumer advocacy groups there like they have in the UK... if you do, you may get some traction with their help, who knows.

http://maps.telstraglobal.com/
http://www.comparebroadband.com.au/a...holesale.htm#.
http://www.telecomramblings.com/file...an12-26-v1.png

[Azmoddon]

The day before yesterday (11/14) many of my FC-mates were complaining about lag spikes. Yesterday and into today (11/15-16) others, including myself, are now affected. Mobs are rubberbanding and forget crafting or gathering like this.

My free month is about up and I can't say this is convincing me to sub, hope it gets fixed soon.

Thanks!

[Devilgunman]

I didn't see this ongoing thread so I will copy what I reported in another thread here

I have been getting constant 90000 error since last week. It keeps kicking me out every 10-15 min or sometime even more frequent. I contacted customer service and their suggestions are not helpful. I've been playing this game for more than a year and never have a problem until now. I'm on PC with wire connection.

This is what I get from tracert

Tracing route to 199.91.189.42 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.1.3.1
3 8 ms 1 ms 1 ms 38.110.218.129
4 1 ms <1 ms 1 ms vl3523.mag01.iah02.atlas.cogentco.com [38.20.41.
5]
5 1 ms <1 ms <1 ms te2-7.mag02.iah02.atlas.cogentco.com [154.54.83.
134]
6 1 ms 1 ms 1 ms te0-0-0-0.rcr12.iah02.atlas.cogentco.com [154.54
.83.129]
7 2 ms 2 ms 2 ms be2145.ccr21.iah01.atlas.cogentco.com [154.54.1.
85]
8 16 ms 16 ms 16 ms be2172.ccr41.atl01.atlas.cogentco.com [154.54.29
.17]
9 28 ms 28 ms 27 ms be2170.mpd21.dca01.atlas.cogentco.com [154.54.31
.106]
10 34 ms 33 ms 34 ms be2518.ccr41.jfk02.atlas.cogentco.com [154.54.80
.161]
11 37 ms 37 ms 37 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.
50]
12 42 ms 42 ms 42 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43
.17]
13 42 ms 42 ms 41 ms 38.122.42.34
14 42 ms 42 ms 42 ms 10.2.2.1
15 42 ms 42 ms 41 ms 192.34.76.2
16 42 ms 43 ms 42 ms 199.91.189.234
17 42 ms 42 ms 42 ms 199.91.189.42

Trace complete.

ps. I also tried playing this game on PS4. Again, 90000 kicked my out.

[Genosuke]

same having 90000 and 90002 often since last month
Server : Excalibur



Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=74ms TTL=46
Reply from 184.107.107.176: bytes=32 time=74ms TTL=46
Reply from 184.107.107.176: bytes=32 time=73ms TTL=46
Reply from 184.107.107.176: bytes=32 time=73ms TTL=46

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 74ms, Average = 73ms

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.100.1
2 6 ms 4 ms 4 ms 10.5.50.174
3 * * * Request timed out.
4 5 ms 4 ms 5 ms fixed-203-69-2.iusacell.net
5 * * * Request timed out.
6 70 ms * 70 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

7 72 ms 202 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

8 73 ms 73 ms 72 ms 4.59.178.62
9 73 ms 74 ms 73 ms te8-3.dr10.mtl.iweb.com [67.205.127.238]
10 71 ms 76 ms 74 ms 72.55.128.44
11 73 ms 72 ms 73 ms 184.107.107.176

Trace complete.

[Iudicium]

I'm having constant lag spikes within instances and in PvP specifically, I get constant 90K. I'm not sure what to do, it's been happening since after the 2.4 patch. It went away for 2 days (yesterday and the day before) but now I'm having issues again. I'm not sure what's changed but I read some of the previous posts and did some traceroutes. I don't know what to do with this information, but here it is:

ISP: Rogers
Country: Canada


Traceroute to lobby servers:

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.0.1
2 * * * Request timed out.
3 11 ms 18 ms 20 ms gw03.flfrd.phub.net.cable.rogers.com [66.185.90.
225]
4 23 ms 39 ms 22 ms so-5-0-3.gw02.bloor.phub.net.cable.rogers.com [6
6.185.81.73]
5 29 ms 32 ms 49 ms 24.156.144.182
6 * * * Request timed out.
7 27 ms 29 ms 30 ms be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.7
3]
8 29 ms 29 ms 28 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
9 47 ms 42 ms 46 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
10 54 ms 34 ms 36 ms 38.122.42.34
11 * * * Request timed out.
12 40 ms 36 ms 80 ms 192.34.76.2
13 38 ms 50 ms 72 ms 199.91.189.234
14 38 ms 1015 ms 35 ms 199.91.189.74

Trace complete.

Tracing route to neolobby04.ffxiv.com [199.91.189.93]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 17 ms 13 ms 12 ms 66.185.90.221
4 22 ms 14 ms 15 ms so-4-0-0.gw02.ym.phub.net.cable.rogers.com [66.1
85.82.125]
5 * * * Request timed out.
6 15 ms 21 ms 46 ms te0-7-0-10.ccr22.yyz02.atlas.cogentco.com [154.5
4.13.141]
7 21 ms 20 ms 15 ms be2373.ccr21.yyz02.atlas.cogentco.com [154.54.46
.33]
8 23 ms 32 ms 31 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
9 42 ms 18 ms 23 ms 38.122.42.34
10 * * * Request timed out.
11 23 ms 20 ms 23 ms 192.34.76.2
12 23 ms 23 ms 40 ms 199.91.189.234
13 36 ms 23 ms 18 ms 199.91.189.93

Trace complete.

Tracing route to neolobby06.ffxiv.com [199.91.189.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 14 ms 12 ms 11 ms gw03.flfrd.phub.net.cable.rogers.com [66.185.90.
225]
4 22 ms 24 ms 22 ms so-5-0-3.gw02.bloor.phub.net.cable.rogers.com [6
6.185.81.73]
5 * * * Request timed out.
6 * * * Request timed out.
7 27 ms 33 ms 30 ms be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.7
3]
8 30 ms 42 ms 1011 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
9 53 ms 52 ms 36 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
10 37 ms 37 ms 51 ms 38.122.42.34
11 * * * Request timed out.
12 39 ms 47 ms 37 ms 192.34.76.2
13 45 ms 38 ms 44 ms 199.91.189.234
14 36 ms 56 ms 38 ms 199.91.189.106

Trace complete.

Traceroute/ping to Adamantoise, where my character is.

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 9 ms 11 ms 15 ms gw03.flfrd.phub.net.cable.rogers.com [66.185.90.
225]
4 20 ms 18 ms 15 ms so-5-0-3.gw02.bloor.phub.net.cable.rogers.com [6
6.185.81.73]
5 * 27 ms 46 ms 24.156.144.182
6 * * * Request timed out.
7 28 ms 25 ms 26 ms be2005.ccr41.ord01.atlas.cogentco.com [66.28.4.7
3]
8 29 ms 28 ms 28 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
9 39 ms 35 ms 35 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
10 39 ms 35 ms 55 ms 38.122.42.34
11 * * * Request timed out.
12 35 ms 35 ms 45 ms 192.34.76.2
13 34 ms 50 ms 35 ms 199.91.189.234
14 36 ms 36 ms 36 ms 199.91.189.30

Trace complete.

Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=36ms TTL=242
Reply from 199.91.189.30: bytes=32 time=36ms TTL=242
Reply from 199.91.189.30: bytes=32 time=39ms TTL=242
Reply from 199.91.189.30: bytes=32 time=51ms TTL=242

Ping statistics for 199.91.189.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 51ms, Average = 40ms

[Tusembobel]

And again the game became unplayable without any free log in weekends.. I could understand if there was one, but lagging out as hell in morning dungeon - it's too much. Mr. Raist are trying to show us some graphs of tracing thru all connection threads on forums, but I really do not care of any tracing; I contacted my provider, and it's all ok with connection untill it comes to things on SE side. They really need to do something..