pool.ntp.org


pool.ntp.org: public ntp time server for everyone

Introduction

Active Servers

As of 2016-12-10

Le projet pool.ntp.org est un grand cluster virtuel de serveurs de temps fournissant des informations fiables facile à utiliser Service NTP pour des millions de clients.

Cette ressources est utilisée par des millions ou dizaines de millions de systèmes à travers le monde. C'est le "serveur de temps" par défaut pour la plupart des grandes distributions Linux et de nombreux appareils en réseau (voire informations pour les fournisseurs).

En raison du grand nombre d'utilisateurs, nous sommes dans le besoin de plus en plus de serveurs. Si vous avez un serveur avec une adresse IP statique toujours disponible sur Internet, s'il vous plaît envisager de l'ajouter au cluster .

Le projet est maintenu et développé par Ask Bjørn Hansen et un grand groupe de contributeurs sur la listes de diffusion. le code source est disponible.

Hébergement bande passante pour les serveurs «hubs» sont actuellement fournies par Develooper.com et Phyber Communications.

remonter

Actualités

Atom feed Subscribe in a reader

  • November 29, 2016

    Equipment failure

    A network switch failed causing an outage for the management system and the NTP Pool website. The DNS and NTP services should only be minorly affected, even if the outage lasts a little while.

    I’ll update status website with updates.

  • November 4, 2016

    NTP Best Current Practices

    The IETF has published a new version of NTP Best Current Practices documenting learned best practices on how to run NTP servers and clients.

    If you know a little about the NTP protocol reading it will be a quick way to learn more about how it works “in the wild” (including on your own systems).

    Some of it is specific to the “reference” ntpd implementation, but much of it will apply to other clients or servers, too.

  • August 27, 2016

    System status page

    Thanks to the kind folks at statuspage.io we now have a system status page. It’s also available at an alternate domain.

    Most of the data is updated manually, so it won’t be any better than the busy humans can manage, but it’ll be a better system for giving system updates than posting here (or on the dicussion mailing list).

    Update Whoops, I completely forgot that ntppool.org is in the HSTS preload list.

    The site was working for me in the browsers I tested. I’ve contacted statuspage.io about getting a TLS cert added, in the meantime ntppool.statuspage.io works.

  • April 23, 2016

    Login upgrade deployed

    The new login system that was tested on the beta site has been enabled on the production site.

    The login system is now using Auth0 to add more login options than yet another username and password. If you have a Github, Google, Microsoft or other supported account you can use that to login.

    If you are one of the many existing users, you have to create a “new account” (sign up again) with the email address you previously used to login to your account. No passwords have been transferred over.

    If you have any trouble, please use the form below the login box and we’ll help.

    Currently if you login with separate accounts that all use the same email address, it will log you into the same account. Support for merging accounts with different verified email addresses might come later.

  • January 4, 2016

    New login system

    This week we’re testing using Auth0 to login on the beta site. This will hopefully make the user account management much easier for everyone.

    The beta site is a full installation of the system running with a separate database that gets new code before the regular site.

    If you have a server running ntpd you can try adding it, even if it’s not a server appropriate for adding to the main pool.

    The healthy servers registered on the beta site do get published in DNS (1.beta.grundclock.com, etc), though nobody should be using those names other than when testing the beta site!

  • Older news...

Links

remonter
Status | Comments and questions to Ask Bjørn Hansenask@develooper.com