@LeoBodnar: Please, for the sake of everyone, stop demanding. The pool is run by volunteers, including the monitoring system code and hosting. If you are right, explain that you are right in a polite, respectful, and constructive manner, and people will listen.
At the risk of repeating @avij’s post but not doing a good job of it, let’s talk about your figures: your graph above shows your server topping out at 110K rps. All clients which query your server when you’re at maximum rps will get dropped - not just those which get dropped due to occasional link congestion as is the case with all UDP. If the monitoring station is one of those, it will get dropped. If it’s other clients they will get dropped. So from the perspective of those clients, your NTP server isn’t responding. And that’s what we see in the CSV record for your server - occasional I/O timeouts.
What you seem to be arguing for is a special exception for your server, that it should be just left in the pool all the time, regardless of its ability to serve clients, because those clients will try again later, and some of them will likely get through (because with a random-ish distribution of requests, different clients will get dropped each time).
This might seem reasonable to you, but can you see how it might not be ideal for those clients who were hoping to get their NTP requests serviced? If there are 3 hosts which are not dropping packets and yours is, it’s much more reasonable to simply drop yours out of the zone when it reaches saturation point, and put it back in when traffic drops a bit. Alternatively, you could tune your bandwidth session down a bit so that your server is just below the threshold of dropping packets. (I recognise this might be hard with the bandwidth levels currently available in the pool management interface, but that’s something that should be relatively easy to improve in the code.)
Manual handling of individual servers isn’t practical for a project like the NTP pool. If you can think of a better approach that doesn’t require manual handling, but can be implemented automatically by the monitoring system, I’m sure everyone would be keen to see your patches to the pool code.