NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
▲I joined the NTP Pool, but not with my Stratum 1 Pi (jeffgeerling.com)
Avamander 1 hours ago [-]
For the price and complexity of building a good Linux-based time server I'd heavily recommend looking at FPGA-based solutions instead. x86 platforms also have PCIe PTM and TGPIO options available[0], which are tad better than the common ARM equivalents and GPIO interrupts.

In general Pi-s are relatively bad for timekeeping. Not just the NIC (which can be replaced by hats with their own), there are also oscillator replacement mods[2] to work around this to some extent. Though all this still leaves many other sources of timekeeping error.

So if the goal is low-cost precise timekeeping, one can assemble something FPGA-based[2] for quite a bit less money, that can reach very low noise figures. You can spend the remaining money on the GNSS antenna and receiver instead.

I'm also sure a FPGA-based approach could be taken even further with some external timekeeping chips available and the FPGA could just do the NTP/PTP protocol stuff.

[0]: https://www.youtube.com/watch?v=zxK0_j2Ah2I [1]: https://raspberrypi.stackexchange.com/questions/74482/switch... [2]: https://fy.chalmers.se/~f96hajo/fakernet/board_Arty_A7-35-GP...

jeffbee 1 hours ago [-]
Back when I thought this was true, I put together an x86 platform with PTM and a fancy NIC and it would hard-lock the bus to such an extent that I had to physically unplug it to recover. There are a lot of pieces required for a complete solution and I'd caution against a categorical statement like "x86 has PTM".
Avamander 12 minutes ago [-]
As I said, tad better, not perfect. I'd say finding reasonably-priced x86 hardware with that functionality is an even bigger hurdle.
bityard 35 minutes ago [-]
I thought I remembered reading that they did not allow VPSes to be part of the pool because of the historical issues around VMs and timing, combined with the fact that the VPS operator could make host-level changes at any time that could impact the accuracy of the host. But now I'm not finding anything about that. Maybe they have enough monitoring and automation that running nptd on bare metal is not a strict requirement anymore?
walrus01 19 minutes ago [-]
I don't recall the details but one of the historical problems with VPSes is that people were trying to use things like openvz VPSes which are more like a glorified chroot/jail, rather than something like a QEMU/KVM VPS (or Xen PVH, or Xen HVM with virtualization extensions).

I still personally wouldn't try to run an NTP server on a VM unless I also owned/controlled the bare metal hardware the hypervisor is running on.

lightswitch05 2 hours ago [-]
Great write up! I too run a stratum 1 and am part of the pool. Except, I have way less interesting hardware. One benefit on going cheap is having multiple stratum 1s then you can have some redundancy and have more interesting local peers to compare results against. I do see a more expensive setup in my future, though.

Anyways, I use NTPSec- which is the default these days on Debian when you apt-get install NTP. I’ve not tried Chrony, but I see it mentioned all the time.

I’m curious what others here are running and their thoughts on the pros and cons?

Edit: I forgot to add, one of my favorite parts of being in the pool is basically a free uptime monitor of my ISP. There have been multiple cases where I see a blip in my offset then a full blown ISP outage within 78 hours of the blip, then a return to my normal offsets after to outage has resolved.

geerlingguy 2 hours ago [-]
In the NTP Pool community, I've seen a few people mention CenterClick NTP servers; I'm happy to do my own DIY builds (Pi or otherwise), but this looks like a nice option for SMBs or time-nuts who don't want to manage their own hardware: https://centerclick.com/ntp/

There are also a lot of people who buy old Spectracom or other 'enterprise' time servers since they can be had for low hundreds of dollars with some nice features like rubidium or OCXO oscillators, so they can hold over time much more accurately when GPS is down, or upstream NTP providers are unreachable.

And regarding chrony, it's the default in many distros now, I like some of its built-in monitoring and clock adjustments, it just feels easier to manage if you want more than just base NTP features. It also supports hardware timestamping if you have network hardware that has it, which IIRC NTPd doesn't? I haven't messed with systemd-timesyncd or ntpd-rs, so can't say much on them.

unsnap_biceps 27 minutes ago [-]
I have around a dozen CenterClick 270s at various locations and I think generally I have one lock up every 6 months or so. A PoE power cycle on the switch recovers it, so overall I've been really happy with them. I believe they're a one-person shop.
Palomides 2 hours ago [-]
I think most people run chrony or ntpd-rs; not part of the pool, but I've been using chrony for a while, and it seems like ntpd-rs's support for PTP (which I "need") is still under development
nahikoa 2 hours ago [-]
Some of the cool kids are moving to https://github.com/pendulum-project/ntpd-rs
zodwick 42 minutes ago [-]
One of those posts which truly hits you in the face and calls you an idiot for how much you don't know. Definitely a rabbit hole I'm going down this week. Thanks
omoikane 1 hours ago [-]
> https://www.jeffgeerling.com/blog/2026/i-joined-the-ntp-pool...

I wonder why the wall clock on top is 10 seconds ahead of the bottom one?

undersuit 22 minutes ago [-]
Relativity. /s
jeffrallen 2 hours ago [-]
PSA: The Swiss government has NTP servers on ntp{11,12,13}.metas.ch.

METAS is the Federal Institute of Metrology.

rmoriz 37 minutes ago [-]
Germany https://www.ptb.de/cms/ptb/fachabteilungen/abt9/gruppe-95/re...

However using a pool is the better way IMHO.

Or go Stratum 1 via DCF77 https://zeit.ptb.de/

aaronax 2 hours ago [-]
What speed did you choose in the pool dashboard? How many request per second are you serving, and do you have a goal for that?
geerlingguy 2 hours ago [-]
I started at 25 Mbit to see how things would go, and found the Oxtrys VPS I have the public server running on could handle that without issue.

Over the past few weeks I bumped it up to 50, then 100, and now it's at 250 Mbit. At 100 Mbit I was seeing 180-250 requests/sec. At 250 (just switched earlier this morning) I'm seeing 500-600 requests/sec.

I'm monitoring things on the server with chronytop[1], a tool I whipped up with Claude since I didn't see any other concise dashboards and hated `watch`ing chronyc sources to get any kind of updated data.

[1] https://github.com/geerlingguy/chronytop

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 19:37:57 GMT+0000 (Coordinated Universal Time) with Vercel.