211ms isn't awful but it isn't great either. However, geographic location in relation to the server can have an impact on this. So the server might be responding fine and if you were closer to the server that ping time may be much lower.
This depends on the server location that you are pinging. The closer the location the better ping time it should be. If the location of the server is pretty close, normal speed would be about 1 ms. For example, pinging server in our datacenter gets ping time 0.042 ms. While pinging server's in Germany it can get 31 ms, while India gets 184 ms.
It all depends on how many different routers the ping needs to go through. More it has to go through, more possibilities for it to have some difficulties or get delayed. That is why the recommendation is to get the server closer to your audience that will be using it.
There is no defined "standard" response time and neither does the ping binary itself claims so, as it depends on many thing including hardware performance, the underlying physical layer quality, and existing traffic conditions.
Anything below a ping of 20ms is considered to be great, while anything over 150ms could result in noticeable lag.
Hello, Chris! As you can see ping time depends on distance to the server you're pinging, besides, on amount of simultaneous connections on the server and bandwidth of your internet connection. For different purposes, there is different acceptable ping time. More often 0,1-40 ms is good ping and you can watch youtube live broadcasts or play multiplayer online games, 40 - 110 ms is less comfortable but still, you can use web-resources normally, 110 - 210 ms such ping remains OK to access websites with texts.
That's an acceptable time (latency). I would start worrying at over 500ms. Contrary to a few replies here, geography has very little to do with high ping latency. There are a number of factors that can cause high latency: Heavy internet traffic at the time, congested/overloaded routers on the way to the target machine, low quality/inadequate bandwidth are the most common causes (not geography).
If you would like to narrow down the cause of your latency run a trace route. It will show you the latency between each hop along the path to your target machine. A spike in latency in one of those hops may indicate the problem device or network.