Unplayable lag and disconnects since October 10

[Kuroka]

Shiva here, same here, every day around 19-22:00 the lag gets real and even others complain about it, its been almost a week now and its not my internet, i can download as fast as usual and watch YT on 1080p while ff14 becomes a slideshow...

[Keyn]

Interesting...

The lags are gone, ping is back to 0% packets loss, and time is much better too:

Pinging 195.82.50.46 with 32 bytes of data:
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=47ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50
Reply from 195.82.50.46: bytes=32 time=46ms TTL=50

Ping statistics for 195.82.50.46:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 47ms, Average = 46ms

It seems that significant delay on hls-b1-link.telia.net is gone for now:

Tracing route to 195.82.50.46 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 2 ms 2 ms 2 ms 91.77.160.1
4 3 ms 3 ms 3 ms 10.109.11.6 [10.109.11.6]
5 3 ms 3 ms 3 ms mag9-cr01-be12.51.msk.mts-internet.net [212.188.1.5]
6 4 ms 4 ms 3 ms a433-cr01-be7.77.msk.mts-internet.net [212.188.28.102]
7 13 ms 12 ms 13 ms mmon-cr01-be1.78.spb.mts-internet.net [212.188.2.53]
8 17 ms 17 ms 17 ms radio-cr01-ae3.78.hel.mts-internet.net [212.188.29.109]
9 19 ms 19 ms 19 ms hls-b1-link.telia.net [62.115.151.194]
10 45 ms 45 ms 45 ms s-bb4-link.telia.net [62.115.123.30]
11 45 ms 45 ms 45 ms ffm-bb2-link.telia.net [62.115.138.105]
12 46 ms 46 ms 46 ms ffm-b10-link.telia.net [62.115.137.211]
13 47 ms 47 ms 47 ms kddi-ic-301630-ffm-b10.c.telia.net [62.115.32.110]
14 45 ms 44 ms 44 ms 195.82.60.29
15 45 ms 45 ms 45 ms 195.82.61.14
16 45 ms 45 ms 45 ms 195.82.50.234
17 46 ms 46 ms 46 ms 195.82.50.46
Trace complete.

[Dynratygus]

Good afternoon and thank you for the reply.

Based on the information provided, it appears the connection error happens during peak hours. During this time, there is a high volume of traffic onto the servers. To get assist with this, please contact your ISP.


Thank you for visiting the Final Fantasy XIV Technical Support Forums.

[Keyn]

To get assist with this, please contact your ISP.

Good morning, Dynratygus!

How can my ISP solve the problem of lost packets and disconnections with game servers overloaded with traffic during peak hours?
My Internet connection is flawless with other games and online services.

[Dynratygus]

Good morning thank you for the reply.

Your ISP will be able to assist in determining what route your network takes to get to the game.

Thank you for visiting the Final Fantasy XIV Technical Support Forums

[Tuchkin]

The name of the problem is... Telia
I suffer from the same packet loss.
Other MMO works fine... but not FF, the network path to which lies through the Telia network (and specifically hls-b1-link.telia.net [62.115.151.194] node).

[Keyn]

Your ISP will be able to assist in determining what route your network takes to get to the game.

Why do I need ISP, when I just posted traceroute, that shows all jumps from my PC to game server?

Telia network seems to be the problem.

Tracing route to 195.82.50.46 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 1 ms 2 ms 2 ms 91.77.160.1
4 3 ms 3 ms 3 ms 10.109.11.6 [10.109.11.6]
5 4 ms 5 ms 3 ms mag9-cr01-be12.51.msk.mts-internet.net [212.188.1.5]
6 4 ms 4 ms 3 ms a433-cr01-be7.77.msk.mts-internet.net [212.188.28.102]
7 13 ms 12 ms 12 ms mmon-cr01-be1.78.spb.mts-internet.net [212.188.2.53]
8 17 ms 17 ms 17 ms radio-cr01-ae3.78.hel.mts-internet.net [212.188.29.109]
9 44 ms 44 ms 44 ms hls-b1-link.telia.net [62.115.151.194]
10 71 ms 70 ms 70 ms s-bb4-link.telia.net [62.115.123.30]
11 * * * Request timed out.
12 72 ms 71 ms * ffm-b10-link.telia.net [62.115.137.211]
13 73 ms 73 ms 72 ms kddi-ic-301630-ffm-b10.c.telia.net [62.115.32.110]
14 70 ms 74 ms 73 ms 195.82.60.29
15 70 ms 70 ms 70 ms 195.82.61.14
16 70 ms 70 ms 70 ms 195.82.50.234
17 71 ms 71 ms 71 ms 195.82.50.46
Trace complete.

[Kuroka]

Update, today it was just fine, after 6 or so days.