# Ip monitor list

**URL:** <https://community.ntppool.org/t/ip-monitor-list/2818>\
**Category:** Server operators\
**Tags:** monitoring\
**Created:** [March 30, 2023, 8:25am UTC](https://community.ntppool.org/t/ip-monitor-list/2818 "2023-03-30T08:25:48Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![erayd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/erayd/32/85_2.png) [@erayd](https://community.ntppool.org/u/erayd)\
**Post date:** [April 3, 2023, 10:39pm UTC](https://community.ntppool.org/t/ip-monitor-list/2818/10 "2023-04-03T22:39:49Z")

</div>

I still use the following strategy. There are always a few IPs on the blocklist as a result - at the moment of this post, there are currently four. That’s on the lower end of what is typical for my server.

> [@What is a reasonable limit?](https://community.ntppool.org/t/what-is-a-reasonable-limit/2460/11):
>
> I personally add anything that hits me with more than 1000 reqs/sec to a 24hr blocklist at my network edge (prevents things like the fortinet bursters sending problematic levels of traffic as far as my server, although I do still save the blocked requests for later analysis). They get a 3000 request burst before the policy is applied. Anything slower than that, I don’t worry about. If reflection abuse becomes a significant problem, then I will revise that limit downwards. My main rationale beh…

---

_[View the full topic](https://community.ntppool.org/t/ip-monitor-list/2818)._