HUGE CONNECTION PROBLEM

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

[Melondra]

Just to let you guys know the problem is not your internet the North American Data Center is running at Max Capacity on most worlds and is currently under Heavy Load.

[EruanMaesti]

I love that when I look on Twitter and other social media I can see that there is a huge amount of people that are unable to log into their FF account but the lodestone says that all the servers are online. If the servers were online a lot of people would be playing the game right now.

[Nimrook]

Was wondering if it was just me so I tried to connect to every other regions datacenter. All were like instantaneously connecting me. NA servers need fixed, like ASAP.

[Brodo_Swaggins]

#TheLaggening http://youtu.be/a01ttXIT5Ps

[Saik]

Problem is most likely not the Servers, but the Level3 Servers in Montreal as they are giving me and other immense dataloss hardly depending on the time accessing them. This would fit the reason some can go in and some can't. If you have WTFast or and other way of routing around that gap use it.