You are not logged in.
Today server's ping is irregular. It's not a server problem, it's connected with the hosting company network. I am sure they are aware of it and it will be solved.
Check your ping to the server.
> ping -n 18 188.165.220.115
Pinging 188.165.220.115 with 32 bytes of data:
Reply from 188.165.220.115: bytes=32 time=33ms TTL=55
Reply from 188.165.220.115: bytes=32 time=197ms TTL=55
Reply from 188.165.220.115: bytes=32 time=187ms TTL=55
Reply from 188.165.220.115: bytes=32 time=204ms TTL=55
Reply from 188.165.220.115: bytes=32 time=188ms TTL=55
Reply from 188.165.220.115: bytes=32 time=198ms TTL=55
Reply from 188.165.220.115: bytes=32 time=33ms TTL=55
Reply from 188.165.220.115: bytes=32 time=33ms TTL=55
Reply from 188.165.220.115: bytes=32 time=159ms TTL=55
Reply from 188.165.220.115: bytes=32 time=223ms TTL=55
Reply from 188.165.220.115: bytes=32 time=187ms TTL=55
Reply from 188.165.220.115: bytes=32 time=192ms TTL=55
Reply from 188.165.220.115: bytes=32 time=34ms TTL=55
Reply from 188.165.220.115: bytes=32 time=35ms TTL=55
Reply from 188.165.220.115: bytes=32 time=34ms TTL=55
Reply from 188.165.220.115: bytes=32 time=34ms TTL=55
Reply from 188.165.220.115: bytes=32 time=181ms TTL=55
Reply from 188.165.220.115: bytes=32 time=195ms TTL=55
Ping statistics for 188.165.220.115:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 223ms, Average = 130ms
Ping is stable
> ping -n 18 188.165.220.115
Pinging 188.165.220.115 with 32 bytes of data:
Reply from 188.165.220.115: bytes=32 time=52ms TTL=54
Reply from 188.165.220.115: bytes=32 time=50ms TTL=54
Reply from 188.165.220.115: bytes=32 time=50ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=48ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=50ms TTL=54
Reply from 188.165.220.115: bytes=32 time=52ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=51ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=50ms TTL=54
Reply from 188.165.220.115: bytes=32 time=50ms TTL=54
Reply from 188.165.220.115: bytes=32 time=49ms TTL=54
Reply from 188.165.220.115: bytes=32 time=56ms TTL=54
Reply from 188.165.220.115: bytes=32 time=69ms TTL=54
Reply from 188.165.220.115: bytes=32 time=51ms TTL=54
Ping statistics for 188.165.220.115:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 69ms, Average = 51ms
Pinging 188.165.220.115 with 32 bytes of data:
Reply from 188.165.220.115: bytes=32 time=99ms TTL=55
Reply from 188.165.220.115: bytes=32 time=81ms TTL=55
Reply from 188.165.220.115: bytes=32 time=100ms TTL=55
Reply from 188.165.220.115: bytes=32 time=75ms TTL=55
Reply from 188.165.220.115: bytes=32 time=98ms TTL=55
Reply from 188.165.220.115: bytes=32 time=95ms TTL=55
Reply from 188.165.220.115: bytes=32 time=100ms TTL=55
Reply from 188.165.220.115: bytes=32 time=93ms TTL=55
Reply from 188.165.220.115: bytes=32 time=93ms TTL=55
Reply from 188.165.220.115: bytes=32 time=98ms TTL=55
Reply from 188.165.220.115: bytes=32 time=87ms TTL=55
Reply from 188.165.220.115: bytes=32 time=105ms TTL=55
Reply from 188.165.220.115: bytes=32 time=88ms TTL=55
Reply from 188.165.220.115: bytes=32 time=90ms TTL=55
Reply from 188.165.220.115: bytes=32 time=92ms TTL=55
Reply from 188.165.220.115: bytes=32 time=84ms TTL=55
Reply from 188.165.220.115: bytes=32 time=97ms TTL=55
Reply from 188.165.220.115: bytes=32 time=96ms TTL=55
Reply from 188.165.220.115: bytes=32 time=83ms TTL=55
Reply from 188.165.220.115: bytes=32 time=95ms TTL=55
Reply from 188.165.220.115: bytes=32 time=85ms TTL=55
Reply from 188.165.220.115: bytes=32 time=87ms TTL=55
Reply from 188.165.220.115: bytes=32 time=95ms TTL=55
Reply from 188.165.220.115: bytes=32 time=97ms TTL=55
Reply from 188.165.220.115: bytes=32 time=86ms TTL=55
Reply from 188.165.220.115: bytes=32 time=90ms TTL=55
Reply from 188.165.220.115: bytes=32 time=87ms TTL=55
Reply from 188.165.220.115: bytes=32 time=97ms TTL=55
Reply from 188.165.220.115: bytes=32 time=84ms TTL=55
Reply from 188.165.220.115: bytes=32 time=98ms TTL=55
Ping statistics for 188.165.220.115:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 105ms, Average = 91ms
i m on 51 ms right now, but twice today, i was swimming from 50-200 ,,,,,,,,digression -bfsm crazy again, numbers up from 64 cant be kicked ,....
i know we are giving you a lot of work to do tuia, so i wasnt going to say anything, but honestly, since the move from 64 players to 70+ , i cant hit anything , even on moongamers, where i had ping 150+ i could aim properly and kill , not that i expect you to change anything, just wanted you to know,because i adapt to planes and tanks, infantry is out of reach for me this way, a few days when it was 64 players, it was very very playable,but, perhaps it s me, when i do "tracert" , i can clearly see, that i pass thru 2 routers here in croatia, and just then it goes to rbx.g1.ai.fr.eu
The ping depends upon network connection you have and the server or ip address you going to ping. If there is no problem the server on the ping means there may be a problem in the internet connection. Based on your results the sent and received packets are same. So It is a good ping. If you face any problem in your ping you can reset modem or router check the ping for ip address or website using the http://www.whoisxy.com/ping.aspx
Good answer