Unplayable lag and disconnects since October 10

Printable View

10-15-2019, 04:25 AM
Keyn

Unplayable lag and disconnects since October 10

Greetings!

I'm playing on Spriggan server (Chaos Datacenter) for over two months already.
The gameplay was fluid, with rare short lags in some dungeons (one time in a week may be).

I played a lot of multi-players content including a lot of 72 players Frontline PvP.
Everything was perfect.

For the last few days the game became literally unplayable on evenings (GMT +3 here)...
I can't play even in instanced dungeons, because I get heavy lag for 10+ seconds all the time, and very often disconnects (Error 90006).
Right now I get lagged and disconnected even while doing simple gathering activities in far regions of the world with no players around...

I have optic cable connection to Internet (300Mbps) and 1Gbps Ethernet LAN from router to my PC.

Here are my SpeedTest results:
http://nshq.net/Pictures/Personal_Ke...2019-10-14.png

Here are my PC specs:
Time of this report: 10/14/2019, 21:54:38
Operating System: Windows 10 Pro 64-bit (10.0, Build 17134)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: X58A-UD9
Processor: Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz (12 CPUs), ~3.3GHz
Memory: 24576MB RAM
Page File: 9498MB used, 22627MB available
DirectX Version: DirectX 12
Video Card name: NVIDIA GeForce GTX 1070

I did not change anything on my PC or local network lately.
Other MMORPG are working as usually, no lag or disconnects.

Please fix that problem with FFXIV, I really like the game and want to play as I did before.

Thank you!
10-15-2019, 04:40 AM
Keyn

Ping statistics to Chaos Datacenter servers:

Pinging 195.82.50.46 with 32 bytes of data:
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Request timed out.
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Request timed out.
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50

Ping statistics for 195.82.50.46:
Packets: Sent = 9, Received = 7, Lost = 2 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 71ms, Average = 71ms

Pinging 195.82.50.51 with 32 bytes of data:
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Request timed out.
Request timed out.
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49
Request timed out.
Reply from 195.82.50.51: bytes=32 time=71ms TTL=49

Ping statistics for 195.82.50.51:
Packets: Sent = 18, Received = 13, Lost = 5 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 71ms, Average = 71ms

Ping statistics to NA Crystal Datacenter servers (to compare):
Pinging 204.2.229.115 with 32 bytes of data:
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51

Ping statistics for 204.2.229.115:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 195ms, Average = 195ms
10-15-2019, 09:12 AM
Keyn

Same ping stats few hours later:

Ping statistics to Chaos Datacenter servers:

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
Request timed out.
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
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 = 21, Received = 20, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 46ms, Average = 46ms

Pinging 195.82.50.51 with 32 bytes of data:
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=45ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49
Reply from 195.82.50.51: bytes=32 time=46ms TTL=49

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

Ping statistics to NA Crystal Datacenter servers (to compare):
Pinging 204.2.229.115 with 32 bytes of data:
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=196ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51
Reply from 204.2.229.115: bytes=32 time=195ms TTL=51

Ping statistics for 204.2.229.115:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 196ms, Average = 195ms

It's 00:00 GMT, so it looks like the connection and lag problem mostly happens during peak time of EU players...
10-15-2019, 03:28 PM
Morgan

Exact same issue there but with Light DC as well.
All ports open, nothing changed etc etc.
10-16-2019, 02:08 AM
Dynratygus

Good morning and thank you for posting in the Final Fantasy XIV Technical Support Forums.

Keyn, what have you tried to alleviate the issue so far? Morgan, where do you experience the disconnection?

Thank you for visiting the Final Fantasy XIV Technical Support Forums.
10-16-2019, 02:54 AM
Keyn

Quote:

Originally Posted by Dynratygus

Keyn, what have you tried to alleviate the issue so far?

Greetings, Dynratygus!

So far I've tried everything I could concerning my home network and ISP connection.
Rebooting my router (both soft and hard reboot), upgrading it's firmware to latest version, pinging and tracerouting my local network, testing speeds to different websites and servers.
Disabled some of my PC software that could influence the connection (like Epig Games Store, Uplay etc.)
Played other MMOs and other online games, sensitive to connection, pinged their servers to try packets losses.
I also changed my Internet Explorer settings according to the recommended in other similar forum threads.

Right now the ping to Chaos Datacenter looks good enough:
Pinging 195.82.50.46 with 32 bytes of data:
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Request timed out.
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50

Ping statistics for 195.82.50.46:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 72ms, Average = 71ms

Traceroute shows that I'm connecting to game servers through european telia.net provider:
Tracing route to 195.82.50.46 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1 (my local room router)
2 <1 ms <1 ms <1 ms 192.168.1.1 (my ISP router)
3 2 ms 2 ms 2 ms 91.77.160.1
4 3 ms 3 ms 6 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 3 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 49 ms 48 ms 54 ms hls-b1-link.telia.net [62.115.151.194]
10 * 71 ms * s-bb4-link.telia.net [62.115.123.30]
11 71 ms 71 ms 70 ms ffm-bb2-link.telia.net [62.115.138.105]
12 72 ms 76 ms 71 ms ffm-b10-link.telia.net [62.115.137.211]
13 72 ms * 73 ms kddi-ic-301630-ffm-b10.c.telia.net [62.115.32.110]
14 77 ms 74 ms 74 ms 195.82.60.29
15 70 ms 70 ms 70 ms 195.82.61.14
16 * * 70 ms 195.82.50.234
17 71 ms 71 ms 72 ms 195.82.50.46
Trace complete.
10-16-2019, 03:27 AM
Morgan

Everywhere. I keep losing packets on EU datacenters. It starts around 4pm ST then escalates as time goes then it stops lagging at roughly 9pm ST.
I already called ISP and tried disabling firewall, defender, etc. Hell, I even reinstalled Windows. Tried to ping servers from laptop - same loss.
I've been running Wireshark today and can post the data I think? Also right now:

Ping statistics for 195.82.50.62:
Packets: Sent = 85, Received = 72, Lost = 13 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 74ms, Average = 71ms
10-16-2019, 03:40 AM
Dynratygus

Good morning and thank you for the reply.

Please try the following:

Open the following ports ranges on your router:
▼TCP
54992 through 54994,
55006 through 55007,
55021 through 55040
These are remote ports in your router’s firewall. They designate what can send information to your PC and what cannot. These specific ports are used by the game to connect to the local client.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.
10-16-2019, 03:40 AM
Morgan

It's been already done.
10-16-2019, 03:52 AM
Keyn

As the evening comes, the lags and packets loss increase:

Pinging 195.82.50.46 with 32 bytes of data:
Reply from 195.82.50.46: bytes=32 time=74ms TTL=50
Request timed out.
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=72ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Request timed out.
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Reply from 195.82.50.46: bytes=32 time=71ms TTL=50
Request timed out.

Ping statistics for 195.82.50.46:
Packets: Sent = 20, Received = 17, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 74ms, Average = 71ms

Currently I'm constantly online since midday, and testing the connection every half an hour.
Daytime connection was absolutely stable, with less than 5% packet losses and no lags.
http://nshq.net/Pictures/Personal_Ke...2019-10-15.jpg
10-16-2019, 04:22 AM
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...
10-16-2019, 07:13 AM
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.
10-16-2019, 08:46 AM
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.
10-16-2019, 01:24 PM
Keyn

Quote:

Originally Posted by Dynratygus

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.
10-18-2019, 01:58 AM
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
10-18-2019, 02:50 AM
Tuchkin

same problem

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).
10-18-2019, 03:30 AM
Keyn

Quote:

Originally Posted by Dynratygus

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.
10-18-2019, 06:03 AM
Kuroka

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