# First night in the pool, hammered by Tesla? **URL:** \ **Category:** Server operators\ **Created:** [November 9, 2026, 5:30am UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845 "2026-11-09T05:30:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![geerlingguy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/geerlingguy/32/2784_2.png) [@geerlingguy](https://community.ntppool.org/u/geerlingguy)\ **Post date:** [November 9, 2026, 5:30am UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/1 "2026-11-09T05:30:54Z")
I finally got my NTP setup working, and after letting it test a while, I set it to 25 Mbps in the server settings. I quickly saw a lot of traffic, and apparently the majority in the first couple hours was from Tesla—including so many packets chrony’s rate limiting started cutting them off: ```auto jgeerling@ntp-01:~$ sudo chronyc -n clients | sort -k3 -rn | head -15 199.120.48.35 4091 2373 6 2 643 0 0 - - 199.120.48.33 4167 2351 5 3 560 0 0 - - 199.120.48.34 3838 2164 6 1 689 0 0 - - 199.120.48.32 3519 1992 5 2 648 0 0 - - 75.49.164.105 792 551 -1 -1 38m 0 0 - - 199.200.87.114 472 321 0 1 29m 0 0 - - 69.135.51.117 462 310 -1 -2 43m 0 0 - - 98.189.254.163 444 291 -3 -1 578 0 0 - - 217.92.158.216 457 280 -2 -3 221 0 0 - - 66.255.209.49 336 210 -2 0 728 0 0 - - 50.84.96.34 292 145 8 -1 441 0 0 - - 167.224.109.178 224 126 -2 -3 20m 0 0 - - 47.229.31.16 224 109 -3 -4 341 0 0 - - 209.71.153.34 208 108 -1 0 29m 0 0 - - 167.142.26.49 144 65 -1 1 164 0 0 - - ``` The 199.x addresses [all belong to Tesla](https://whois.arin.net/rest/net/NET-199-120-32-0-1). I figured I’d see some crazy stuff but not within the first few minutes of joining the pool! My server’s up here: [pool.ntp.org: Statistics for 207.244.255.245](https://www.ntppool.org/scores/207.244.255.245) But now a question for those who’ve been in the pool longer: is my rate limiting configuration for chrony correct? I didn’t want to set it too open, though I know chrony does a better job limiting NTP-based attacks than some older ntpd setups… `ratelimit interval 1 burst 16` ---
**Author:** ![gombadi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/gombadi/32/1486_2.png) [@gombadi](https://community.ntppool.org/u/gombadi)\ **Post date:** [November 9, 2026, 8:45am UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/2 "2026-11-09T08:45:57Z")
> [@geerlingguy](#): > > is my rate limiting configuration for chrony correct? At the time of looking the servers score was 15.5 and slowly climbing so early days. One thing I have noticed is there is no such thing as one size fits all. A setting that works in one part of the world would not work that well in another. As an initial setting it looks good but it would pay to keep an eye on things over the next few weeks to see if there are any issues. The US has quite a few servers in the pool so being one of many gives some protection from load spikes. I would also be interested to hear how your hosting goes over the next few months. It seems you are with `OrgTechName: Contabo Tech`. Some people seem to have no problems with them while others have a different experience. I think the hosting company and its network connections can have a large influence over the quality of the time being served. Anyway have fun timing the world 🙂 ---
**Author:** ![joshlucien](https://avatars.discourse-cdn.com/v4/letter/j/8e7dd6/32.png) [@joshlucien](https://community.ntppool.org/u/joshlucien)\ **Post date:** [November 9, 2026, 2:04pm UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/3 "2026-11-09T14:04:16Z")
@geerlingguy Welcome to the pool! I’m curious about this as a relatively new pool member myself…I’ve set my config as follows: ```auto ratelimit interval 6 burst 8 ``` I believe that corresponds to the expected “nice” behavior of pool clients, and I haven’t seen any errors yet - but I’m here to learn! ---
**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:** [November 9, 2026, 3:18pm UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/4 "2026-11-09T15:18:35Z")
> [@geerlingguy](#): > > ratelimit interval 1 burst 16 No, as you set the polling rate to 2^1 seconds between, meaning people can poll every 2 seconds. This can have a big impact on your system(s). Most people set interval to 4~6 to make polling only allowed 2^4 seconds, meaning once every 16 seconds is allowed. Setting the burst to 16 is also not a good idea as they can poll 16 times real fast, better is 6~8 burst at a time. This bursting is for making an ntp-client sync faster with the correct time. > [@joshlucien](#): > > I believe that corresponds to the expected “nice” behavior of pool clients, and I haven’t seen any errors yet - but I’m here to learn! You won’t see errors, as abusive clients will be dropped. In the log-file you can find them. Most clients behave, but there are a few bad out there and can bring your system down if you allow them to keep polling at a high rate. Beware, the load can go very high when you allow fast polling by default. ---
**Author:** ![geerlingguy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/geerlingguy/32/2784_2.png) [@geerlingguy](https://community.ntppool.org/u/geerlingguy)\ **Post date:** [November 9, 2026, 3:19pm UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/5 "2026-11-09T15:19:57Z")
I actually purchased the VPS through Oxtrys (never tried them before) since it said they have a US datacenter in St. Louis — I have that VPS set up with a wireguard tunnel to my studio Time Pi directly (didn’t want to expose my studio’s fiber directly to the world). Ping times are \< 3ms between the STL datacenter and here, but external requests go through Contabo’s Chicago network, unfortunately. So 15+ ms round trip for some requests because of that 😕 But so far I haven’t hit any rate limiting or weird situations. I’ll have to see how it goes over the next few months. ---
**Author:** ![geerlingguy](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/geerlingguy/32/2784_2.png) [@geerlingguy](https://community.ntppool.org/u/geerlingguy)\ **Post date:** [November 9, 2026, 3:22pm UTC](https://community.ntppool.org/t/first-night-in-the-pool-hammered-by-tesla/4845/6 "2026-11-09T15:22:21Z")
I’d rather be generous with the polling; I had considered raising that limit more, but since this is on shared infrastructure I wanted to leave a sane limit. Since I’ve done a number of tests in the past on direct NTP servers, where it might be useful to poll once per second for a minute or two, I’m okay with letting others do that on this server. If I see abuse, I’ll raise the limits of course. But for now it seems the limits I have in place are stopping a lot of that already: ```auto jgeerling@ntp-01:~$ sudo chronyc -n clients | sort -k3 -rn | head -15 192.80.114.240 13587 9583 7 1 380m 0 0 - - 204.63.214.21 4944 3686 -2 -1 97m 0 0 - - 192.80.114.242 3364 1966 6 0 406m 0 0 - - 12.150.106.71 2640 1861 -3 -1 47m 0 0 - - 12.160.27.66 2172 1591 8 10 55m 0 0 - - 96.4.232.218 1920 1350 -2 0 31m 0 0 - - 96.4.232.211 1760 1219 -2 -1 31m 0 0 - - 96.4.232.212 1712 1147 -4 -3 31m 0 0 - - 96.4.232.220 1616 1122 -2 -1 31m 0 0 - - 198.41.70.123 1428 1002 -1 0 116m 0 0 - - 47.47.162.234 1280 924 -5 -5 364m 0 0 - - 73.146.94.51 2888 905 -1 2 241m 0 0 - - 179.1.181.242 1264 862 -1 -1 451m 0 0 - - 65.51.243.86 1248 855 -2 -1 370m 0 0 - - 12.106.225.194 1256 794 -3 -1 34m 0 0 - - ```