# Steady traffic increase BE since around midnight CET yesterday **URL:** \ **Category:** Server operators\ **Created:** [December 13, 2025, 10:30am UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182 "2025-12-13T10:30:37Z")\ **Posts on this page:** 13\ **Page:** 3
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 20, 2025, 2:29pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/45 "2025-12-20T14:29:05Z")
I mean for the tiny servers that are only listed once every minute or so, maybe tad higher value. And high values for BIG servers. That way we drop out of the DNS-cache pretty quickly. Just an idea…no idea of it actually works. As I do believe DNS-servers can override it to avoid low TTL’s. ---
**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:** [December 20, 2025, 3:47pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/46 "2025-12-20T15:47:06Z")
If you want to see the “aa” flag (and the default 130 second TTL) you need to query the authoritative servers of that zone. For example “dig @a.ntpns.org [be.pool.ntp.org](http://be.pool.ntp.org)”. Other than that, the caching you have seen is how DNS works and there’s nothing unusual in how the pool does DNS in this regard. DNS is a textbook example of how things scale to Internet scales, and caching nameservers is an important part of it. ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 20, 2025, 3:54pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/47 "2025-12-20T15:54:37Z")
> [@avij](#): > > dig @a.ntpns.org [be.pool.ntp.org](http://be.pool.ntp.org) Yes you are right. Did not know that. Thanks. ---
**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\ **Post date:** [December 21, 2025, 7:15pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/48 "2025-12-21T19:15:41Z")
I’ve added my IPv6 BE server with a `2.0 GBit` netspeed again. Any improvements in the traffic load for IPv6? ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 22, 2025, 4:08pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/49 "2025-12-22T16:08:34Z")
I have stopped serving IPv6 from my home for Belgium. But my other larger servers do that, stratum 2. I did ask all my servers to be added to Belgium, sadly no response yet. As I probably set the speed a lot higher when they all are assinged to BE as well. However, my big server has been limited to 6mbit: > **[pool.ntp.org: Statistics for 2001:1b60:2:1:1126:104:0:1](https://www.ntppool.org/scores/2001:1b60:2:1:1126:104:0:1)** To prevent spikes. I wonder how much load your IPv6 server is getting now. I think you better check your own server for load, maybe show graphs? I have no graphs running on that server. Sorry. ---
**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\ **Post date:** [December 22, 2025, 5:36pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/50 "2025-12-22T17:36:24Z")
Had the IPv4 side of the server at 1.5GBit until roughly noon yesterday, I believe, to see whether the rate would keep increasing, and for potential comparison with @stevesommars’ server kept at the same rate through Saturday at least. Unfortunately some hiccups on the provider side, as visible in the graph, so not sure how reliable the data is. ![Screenshot from 2025-12-22 18-23-56](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/7/74b0a8956738a09eddcb5d3d579e6395b26dad37.png) The graph for the IPv6 side of the server, which was at 3Gbit throughout. Diurnal pattern visible, and the various hiccups on the provider side. ![Screenshot from 2025-12-22 18-28-13](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/7/79bf65c6d7f424d36e2ba36e1f7a096e9503efdd.png) ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 22, 2025, 5:53pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/51 "2025-12-22T17:53:06Z")
That is what I see happening here. IPv4 is fairly consitant in requests. But IPv6 spikes. I not know why, I presume a lot of GSM traffic, where typical networktraffic is via Fiber/DSL/Cable and being consistant IPv4 by default. But you set it very high, then you get the max requests. My tiny homeserver is set low, but gets spikes far beyond the setting. Even killing local networkspeed due to this. I put the MikroTik back, as the Fritzbox wasn’t able to handle it. Wanted to test both, but the slowdowns happened again. NAT-table-overload, no other way to name it. I wonder. If you just serve The Netherlands, nothing special, just set it the same. Will the same setting give the same requests? No offense, there are other countries too, but NL is over-serviced. So to see what such speedsettings would do, would reveil a lot (in my opnion). It would give much data to improve the pool of starving of servers and other countries over-served to share the load. Ergo, what happens if you do the same to NL servers, if you can, without serving BE too. ---
**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\ **Post date:** [December 22, 2025, 8:25pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/52 "2025-12-22T20:25:43Z")
Server is a chrony instance which is running on router itself. Don’t have a monitoring service running to collect statistics or create these nice graphs. chrony serverstats gives over a 3.5 hr time period: NTP daemon TX timestamps : 3095430 NTP kernel RX timestamps : 3095430 This translates to 246 NTPreq/s ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 22, 2025, 8:27pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/53 "2025-12-22T20:27:32Z")
Seems rather low to me… ---
**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\ **Post date:** [December 22, 2025, 8:30pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/54 "2025-12-22T20:30:58Z")
Could it be that rates are still ramping up? Current client distribution stats indicate that server IP is part of 2.7% of BE DNS requests but only contributing 5.5% of the bandwidth in BE zone. ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/2/2b4b098ad965acdf781aa1fa60b5652f91ada567.png) ---
**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:** [December 22, 2025, 8:39pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/55 "2025-12-22T20:39:33Z")
For chrony, instead of those “RX/TX timestamps” fields, the “NTP packets received” and “NTP packets dropped” give a better view of the actual amount of traffic. ---
**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\ **Post date:** [December 22, 2025, 8:46pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/56 "2025-12-22T20:46:15Z")
This is 7 mins worth of data: NTP packets received : 104768 NTP packets dropped : 184 Command packets received : 354 Command packets dropped : 0 Client log records dropped : 0 NTS-KE connections accepted: 0 NTS-KE connections dropped : 0 Authenticated NTP packets : 0 Interleaved NTP packets : 0 NTP timestamps held : 0 NTP timestamp span : 0 NTP daemon RX timestamps : 0 NTP daemon TX timestamps : 104584 NTP kernel RX timestamps : 104584 NTP kernel TX timestamps : 0 NTP hardware RX timestamps : 0 NTP hardware TX timestamps : 0 ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [December 24, 2025, 6:49pm UTC](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182/57 "2025-12-24T18:49:48Z")
> [@Kets\_One](#): > > Server is a chrony instance which is running on router itself. Don’t have a monitoring service running to collect statistics or create these nice graphs. > > chrony serverstats gives over a 3.5 hr time period: > NTP daemon TX timestamps : 3095430 > NTP kernel RX timestamps : 3095430 > This translates to 246 NTPreq/s That is not a lot. Look here: > **[Statistics - NTP & NTS Time Server of BOINC Team Belgium](https://ntp.teambelgium.net/ntpstats)** > > NTP & NTS Time Server of Team Belgium 1400req/sec, if you set high speed, it should give high req’s. Like Magic is showing. Maybe your router can’t handle it? Just guessing. BTW, I went back to the DrayTek as MikroTik slows down too and RouterOS is driving me nuts 😵‍💫 [Previous page](https://community.ntppool.org/t/steady-traffic-increase-be-since-around-midnight-cet-yesterday/4182.md?page=2)