- Afrique 34
- Asie 170
- Europe 2602
- Amérique du Nord 881
- Oceania 83
- Amérique du Sud 48
- Mondial 3579
- Tous les Réservoirs de Serveurs 3822
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 a>.remonter
April 23, 2016
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
The beta site is a full installation of the system running with a separate database that gets new code before the regular site.
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!
December 22, 2014
As you might have seen a few days ago several potentially critical security vulnerabilities in all versions of ntpd were announced.
Most OS’es have released back-ported fixes. Depending on your specific ntp and network configuration you might not be exposed, but the easiest way to make sure your systems aren’t vulnerable is to apply the software updates and make sure ntpd has restarted on the fixed version.
Alternatively you can read the announcement page linked above carefully and make configuration changes to mitigate the issues.
If you have built ntpd from source, the easiest fix is to update to 4.2.8. If you have trouble building that version, there’s a “4.2.8p1-beta1” version available now from support.ntp.org as well with some fixes.
January 12, 2014
If you are using the standard ntpd daemon to serve time to the public internet, it’s important that you make sure it is configured to not reply to “monlist” queries. Many routers and other equipment are included in this.
The configuration recommendations include the appropriate “restrict” lines to disallow any management queries to ntpd. Most Linux distributions will have an updated version by now that just disables the “monlist” queries, that will also solve the primary problem.
The NTP Support wiki has more information.
If you operate a network you can use the Open NTP Project to see if you have vulnerable devices on your network.
June 28, 2013
This week we had a period of weird behavior for the monitoring system for (mostly) German IPv6 servers.
After much back and forth on the mailing list and numerous debugging sessions we got this information from a network engineer at Hurricane Electric:
A bug was recently discovered in Force10 switches that cause unicast IPv6 NTP traffic to be erroneously broadcast to all ports. Due to this, there are currently access lists in place preventing some IPv6 NTP traffic from traversing the DECIX exchange, as it was causing a storm that generated nearly 1 terabit per second of traffic. This should be resolved in the near future.
The number of IPv6 servers active in the pool appears to be about back to normal.
Also this is the answer to “why don’t we have IPv6 servers by default on all the pool zones” yet. As you might know only “2.pool.ntp.org” (and 2.debian.pool.ntp.org, etc) returns AAAA records currently.
- Older news...
- Terms of service
- NTP home - the website about ntp
- Meinberg, makers of incredibly fine time server systems.
- The Public servers abuse and the Fixing the NTP server abuse problem threads on the comp.protocols.time.ntp newsgroup have caused this project to be started.