Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Looking for small VPS to contribute to ntppool.org, particularly in less popular locations
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Looking for small VPS to contribute to ntppool.org, particularly in less popular locations

Hello,

after collecting some low end deals I decided that the best way I can give back to the community is to run public NTP servers as part of the ntppool.org project. So my Christmas time mission is simple: collect more small boxes for a low price or if someone wants to giveway their idler or if a provider wants to sponsor one, that will be obviously the most welcome :)

You can check out my profile at https://www.ntppool.org/a/jnd and I promise you all collected servers here will be contributed right there for a good cause and regularly maintained - I'm donating my time too. Running a NTP server doesn't need a lot of power or memory, it can still serve million clients at peak, but has some specific requirement to be useful:

  • As it should be long term reliable service I need at least yearly plan, longer is nicer
  • One stable IPv4, IPv6 is welcome but ultimately not needed as most client still use mainly IPv4
  • Port 123 open, this should be easy but I saw one provider explicitly blocking the port for some reason
  • 1 core, 512 MB to 1 GB RAM is enough, in underserved regions the weaker cpu might be loaded more heavily, going over 50% at working hours
  • Traffic is more important, 1 TB/month is the bare minimum (average sustained 3Mbps, don't need more than 100Mbit for peaks). Unfortunately the underserved regions like India and Asia in general would use significantly more, otherwise I have to throttle down the ntppool DNS reply rate but I understand the traffic is expensive there
  • Only not so well served locations are needed, which means: Outside of EU, Asia besides Singapore, Oceania besides Australia, Africa outwside of South Africa, South America (possibly outside of Brazil), Mexico and other states around there. USA and Canada look well covered but my couple servers there still manage to pull 5-10 Mb/s on average if I leave it on full throttle so maybe there's a little demand for more too. See https://www.ntppool.org/zone/@ and click around to get an idea
  • My budget is generally up to $20 per year but the less it will cost the more of them I can afford to buy and give to the ntppool project. I'd rather choose quality over quantity in places where it's needed the most (and where are not outright dictatorships) but all offers are welcome!

Example of nonsustainable rate (traffic cap wise) on my well loaded Mumbai VPS :) :

Comments

  • Not much point, it won't be accurate and you'll need 2-3 better servers to get time from.

  • @TimboJones said:
    Not much point, it won't be accurate and you'll need 2-3 better servers to get time from.

    Why do you think it won't be accurate? I offer high quality service running modern Chrony which is tracking hand picked collection of mostly close by stratum 1 servers. It usually gets you sub 5 millisecond accuracy on the first sync from loaded server already and then it gradually gets better over time as the network delays and jitter get filtered out, sub millisecond accuracy is definitely possible. Of course your client will use multiple sources and pick the most accurate ones, that's the whole point of the NTP pool.

    For example my basic Virmach Ryzen node now handles steady stream of 10 Mb/s up and 10 Mb/s down, load is around 25% and it's tracking very well:

    chronyc tracking
    Reference ID    : AD474447 (pool-173-71-68-71.cmdnnj.fios.verizon.net)
    Stratum         : 2
    Ref time (UTC)  : Thu Dec 26 15:30:42 2024
    System time     : 0.000054365 seconds slow of NTP time
    Last offset     : -0.000030494 seconds
    RMS offset      : 0.000070545 seconds
    Frequency       : 16.133 ppm slow
    Residual freq   : -0.000 ppm
    Skew            : 0.011 ppm
    Root delay      : 0.004118045 seconds
    Root dispersion : 0.001534154 seconds
    Update interval : 1043.9 seconds
    Leap status     : Normal
    
    chronyc sourcestats
    Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
    ==============================================================================
    pool-173-71-68-71.cmdnnj>  19  10  310m     -0.002      0.018    +24us   115us
    50.205.57.38               17   7  275m     +0.000      0.011    -77us    54us
    pool-173-73-96-68.washdc>  16   7  258m     -0.009      0.062    +18us   240us
    time.falk.us               25  13  413m     +0.012      0.065  +1276us   646us
    time.keneli.org            25  13  430m     -0.017      0.053  +1907us   521us
    bonehed.lcs.mit.edu         6   3   86m     -0.016      0.045    +65us    23us
    ool-43500f49.dyn.optonli>  53  27   16h     -0.037      0.025   +768us   878us
    clock.nyc.he.net           21  10  344m     +0.006      0.010   +322us    72us
    ool-18b97a39.dyn.optonli>  22  18  362m     +0.008      0.056   -344us   450us
    khronos.nis.portalus.net   54  36   17h     -0.040      0.030  +1265us  1219us
    
    chronyc serverstats
    NTP packets received       : 2490562904
    NTP packets dropped        : 0
    Command packets received   : 94
    Command packets dropped    : 0
    Client log records dropped : 24087862
    NTS-KE connections accepted: 0
    NTS-KE connections dropped : 0
    Authenticated NTP packets  : 0
    Interleaved NTP packets    : 23853
    NTP timestamps held        : 4096
    NTP timestamp span         : 4743
    

    I think it looks prety good isn't it?

    Thanked by 1TimboJones
Sign In or Register to comment.