# Slow ramp-up of monitoring score

**URL:** <https://community.ntppool.org/t/slow-ramp-up-of-monitoring-score/1559>\
**Category:** Pool Development\
**Created:** [January 30, 2020, 8:25am UTC](https://community.ntppool.org/t/slow-ramp-up-of-monitoring-score/1559 "2020-01-30T08:25:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\
**Post date:** [January 30, 2020, 8:25am UTC](https://community.ntppool.org/t/slow-ramp-up-of-monitoring-score/1559/1 "2020-01-30T08:25:26Z")

</div>

When there is a negative sample (for example transit network trouble) the score drops a lot. After a positive monitoring sample the score of a server increases only with small quantity. What is the reasoning behind that asymmetry?

---

<div class="post-metadata">

**Author:** ![alica](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/alica/32/337_2.png) [@alica](https://community.ntppool.org/u/alica)\
**Post date:** [January 30, 2020, 8:55am UTC](https://community.ntppool.org/t/slow-ramp-up-of-monitoring-score/1559/2 "2020-01-30T08:55:36Z")

</div>

> [@NTPman](#):
>
> What is the reasoning behind that asymmetry?

To quickly remove the unresponsive server. If it takes hours to remove a (possibly) defective server, clients will receive no time from this server in this rather long period. After the removal, the affected server must show its healthiness long enough to be included in the pool again.