# Collapse of Russia country zone

**URL:** <https://community.ntppool.org/t/collapse-of-russia-country-zone/3607>\
**Category:** Server operators\
**Created:** [November 15, 2024, 12:52pm UTC](https://community.ntppool.org/t/collapse-of-russia-country-zone/3607 "2024-11-15T12:52:08Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![kkursor](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/kkursor/32/1539_2.png) [@kkursor](https://community.ntppool.org/u/kkursor)\
**Post date:** [November 15, 2024, 4:48pm UTC](https://community.ntppool.org/t/collapse-of-russia-country-zone/3607/28 "2024-11-15T16:48:23Z")

</div>

> [@timz](#):
>
> The request rate from each of that IPs was high enough to exhaust conntrack connection limit of typically configured linux firewall, after which the monitor excluded the server from the pool of active servers.  
> Step by step the monitor rearranged traffic to a new victim, amplifying the attack with traffic from good behaving clients.

At least [this guy](https://community.ntppool.org/t/can-i-flood-ddos-ru-pool-ntp-org-to-protest-against-russian-invasion-of-ukraine/2411/4) wanted to shut down RU zone by malicious activity. I think that he is not the only one who thought about that.

---

_[View the full topic](https://community.ntppool.org/t/collapse-of-russia-country-zone/3607)._
