# Modem/Routers slowdown on heavy traffic

**URL:** <https://community.ntppool.org/t/modem-routers-slowdown-on-heavy-traffic/4224>\
**Category:** Server operators\
**Created:** [January 7, 2026, 3:44pm UTC](https://community.ntppool.org/t/modem-routers-slowdown-on-heavy-traffic/4224 "2026-01-07T15:44:26Z")\
**Posts on this page:** 1\
**Showing post:** 65

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [January 17, 2026, 6:32pm UTC](https://community.ntppool.org/t/modem-routers-slowdown-on-heavy-traffic/4224/65 "2026-01-17T18:32:22Z")

</div>

> [@Discussion of client traffic in BE (Belgium) zone](https://community.ntppool.org/t/discussion-of-client-traffic-in-be-belgium-zone/4229/8):
>
> But as I need Voip as well, I can’t reduce it under 30s.

Why not? The time limit is not the maximum length of the session, but the time the session is idle before it gets cleared. The VoIP connection state will stay active in the router as long as there’s a call going on. I suggested 16 seconds earlier (due to DNS timeouts). Maybe try that value and see if everything still works.

---

_[View the full topic](https://community.ntppool.org/t/modem-routers-slowdown-on-heavy-traffic/4224)._