WaaiFu
Veteran Member
haha floating heart goes brrr
Posts: 412
|
Post by WaaiFu on Aug 17, 2019 15:53:07 GMT
A few weeks ago, I get a consistent 4 bars ping, but nowadays I keep getting disconnected for timing out.
What happens is, when I join, the chat lags like crazy, my chat messages that I send DOES go through, but nothing pops up, it only welcomes me, shows my login message and then locks up.
I've seen many other ops experiencing this, what exactly is causing this?
|
|
Lemon
Veteran Member
Insert status here.
Posts: 2,491
| Likes: 2,165
|
Post by Lemon on Aug 17, 2019 16:17:34 GMT
Next time this happens, do a ping command to play.totalfreedom.me and show the output please
|
|
WaaiFu
Veteran Member
haha floating heart goes brrr
Posts: 412
|
Post by WaaiFu on Aug 17, 2019 16:31:19 GMT
Next time this happens, do a ping command to play.totalfreedom.me and show the output please  |
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
Post by _Windows on Aug 18, 2019 13:36:14 GMT
Detailed results from my end. Overall 62% packet loss, but latency is normal. I'd recommend checking network usage on the server if possible.
ping -t play.totalfreedom.me
Pinging play.totalfreedom.me [51.15.61.39] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=114ms TTL=47
Reply from 51.15.61.39: bytes=32 time=111ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=121ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=120ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 51.15.61.39:
Packets: Sent = 27, Received = 10, Lost = 17 (62% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 121ms, Average = 114ms
|
|
StevenNL2000
Forum Admin 
Posts: 6,415
| Likes: 6,936
IGN: StevenNL2000
Timezone: UTC+01:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by StevenNL2000 on Aug 18, 2019 13:52:21 GMT
Detailed results from my end. Overall 62% packet loss, but latency is normal. I'd recommend checking network usage on the server if possible. ping -t play.totalfreedom.me
Pinging play.totalfreedom.me [51.15.61.39] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=114ms TTL=47
Reply from 51.15.61.39: bytes=32 time=111ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=121ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=120ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 51.15.61.39:
Packets: Sent = 27, Received = 10, Lost = 17 (62% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 121ms, Average = 114ms
I didn't know we were having this problem, but it's clearly pretty severe. Pinging play.totalfreedom.me [51.15.61.39] with 32 bytes of data:
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=36ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=33ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=35ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=36ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=33ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Ping statistics for 51.15.61.39:
Packets: Sent = 100, Received = 53, Lost = 47 (47% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 36ms, Average = 34ms
|
|
square
Veteran Member
Asst. Creative Designer
Posts: 1,294
| Likes: 1,291
|
Post by square on Aug 18, 2019 14:29:13 GMT
Next time this happens, do a ping command to play.totalfreedom.me and show the output please  nice |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 18, 2019 17:19:24 GMT
fuck scaleway is being a piece of shit rn
|
|
?Robin
Club 4000 Member
caleb get off of tf
Posts: 8,027
| Likes: 8,604
|
Post by ?Robin on Aug 18, 2019 18:05:22 GMT
Detailed results from my end. Overall 62% packet loss, but latency is normal. I'd recommend checking network usage on the server if possible. ping -t play.totalfreedom.me
Pinging play.totalfreedom.me [51.15.61.39] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Reply from 51.15.61.39: bytes=32 time=114ms TTL=47
Reply from 51.15.61.39: bytes=32 time=111ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=121ms TTL=47
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=120ms TTL=47
Reply from 51.15.61.39: bytes=32 time=113ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 51.15.61.39:
Packets: Sent = 27, Received = 10, Lost = 17 (62% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 121ms, Average = 114ms
I didn't know we were having this problem, but it's clearly pretty severe. Pinging play.totalfreedom.me [51.15.61.39] with 32 bytes of data:
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=36ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=33ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=35ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=36ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=33ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Reply from 51.15.61.39: bytes=32 time=34ms TTL=54
Ping statistics for 51.15.61.39:
Packets: Sent = 100, Received = 53, Lost = 47 (47% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 36ms, Average = 34ms
i'm getting the same issue, and it's in relation to this: status.scaleway.com/index.php/ i've sent a ticket to see why we're getting absolute dropoouts instead of increased latency |
|
WaaiFu
Veteran Member
haha floating heart goes brrr
Posts: 412
|
Post by WaaiFu on Aug 19, 2019 5:12:02 GMT
nice thank |
|
