Might have something with the server to do, i just moved it to Sweden (My VPS provider supports moving of openvz boxes) here is new feedback on ping
NeoRouter
Code:
Pinging 13.37.0.19 with 32 bytes of data:
Reply from 13.37.0.19: bytes=32 time=82ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=41ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=36ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=109ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=44ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=97ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Ping statistics for 13.37.0.19:
Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 109ms, Average = 37ms
Public ip:
Code:
Pinging lillecarl.ath.cx [31.192.227.181] with 32 bytes of data:
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Ping statistics for 31.192.227.181:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 33ms, Average = 31ms
Seems like neorouter just have a few ms higher, which does not matter in my case (everything under 150 is good imo)
This is to wone of my friends:
Code:
Pinging 13.37.0.10 with 32 bytes of data:
Reply from 13.37.0.10: bytes=32 time=272ms TTL=128
Reply from 13.37.0.10: bytes=32 time=254ms TTL=128
Reply from 13.37.0.10: bytes=32 time=354ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=275ms TTL=128
Reply from 13.37.0.10: bytes=32 time=245ms TTL=128
Reply from 13.37.0.10: bytes=32 time=270ms TTL=128
Reply from 13.37.0.10: bytes=32 time=75ms TTL=128
Reply from 13.37.0.10: bytes=32 time=78ms TTL=128
Reply from 13.37.0.10: bytes=32 time=410ms TTL=128
Reply from 13.37.0.10: bytes=32 time=223ms TTL=128
Reply from 13.37.0.10: bytes=32 time=311ms TTL=128
Reply from 13.37.0.10: bytes=32 time=72ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=75ms TTL=128
Reply from 13.37.0.10: bytes=32 time=336ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=318ms TTL=128
Reply from 13.37.0.10: bytes=32 time=77ms TTL=128
Reply from 13.37.0.10: bytes=32 time=123ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=110ms TTL=128
Request timed out.
Ping statistics for 13.37.0.10:
Packets: Sent = 23, Received = 18, Lost = 5 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 410ms, Average = 215ms
Do this mean his connection is awful? And if i choose tcp/udp the data does not go trough NeoRouter, am i right?
EDIT: Regarding CPU usage, i
think OpenVZ does allocate CPU's per user, but you are right about network to 100%. Tho, i do not have the money to rent a dedicated server :/
Thanks again
- Carl