NTP — Network Time Protocol

ntp.inetstat.net is an open access stratum 2 NTP server. NTP is the standard Internet protocol for high precision time synchronisation across the Internet, typically achieving 1-50ms accuracy, or better. SNTP (Simple Network Time Protocol) is a simpler subset of NTP for clients who do not require high precision, just a relatively simple time sync to the nearest second.

This service is provided for the general good of the Internet, but may be withdrawn without notice if it is abused. Please respect the spirit in which open access NTP servers are offered and realise that access to these servers is a privilege, not a right. See the rules of engagement below. Abuse will not be tolerated and abusers will be banned summarily.

Why have I reached this page?

You may have reached this page unexpectedly while looking for information on the pool.ntp.org project. The correct URL for the project web site is http://www.pool.ntp.org/. iNetStat.net is not responsible for the operation of pool.ntp.org — we merely provide a server in the pool.

Location

This server is located in Roubaix, France, on the OVH network, accepting both IPv4 and IPv6 traffic. It runs the standard ntp daemon from ntp.org, currently on version 4.2.6. It should offer reasonably good NTP performance across the EU. People outside the EU should really seek a server closer to them, as NTP precision degrades quite a bit once you are talking about trans-continental / trans-oceanic distances (it's still going to give significantly better than 1s accuracy under normal circumstances, but you'll get much better results from nearby servers, as well as avoiding inefficiently utilising the finite trans-continental and trans-oceanic resources).

Rules of Engagement

• This service is provided on a best effort, voluntary basis only. It should not be relied upon for mission-critical or safety-critical applications. iNetStat.net offers no warranty, express or implied, and accepts no liability for any loss incurred, directly or indirectly, through any failure or withdrawal of this service. If you require a completely reliable and stable service for critical applications, you must establish your own stratum 1 servers.
• This service only provides time information via NTP or SNTP, and not via any other network protocol. Attempting to synchronise time from this server using any protocol other than NTP or SNTP constitutes network abuse. Specifically, RFC868 — Time Protocol and "htpdate" (a kludge of a program to obtain time via HTTP, a protocol which was never intended to be usable for time synchronisation) are prohibited. This service is not advertised as a multi-protocol time service, and access using any protocol other than NTP/SNTP is unauthorised.
• NTP and SNTP do no require frequent or brute force polling. If your host sends more than 100 time queries (packets) in 1 hour, it will be automatically blocked for a period of time. A properly configured NTP/SNTP client should send no more than an initial burst of 8 packets, with minimum interval between packets of 2 seconds, followed by a maximum of 1 packet per minute thereafter. This includes retries — if no response is received to a query packet, the client MUST wait until the next poll interval (minimum 60 seconds), or it will be automatically blocked.
• Any client which causes a spew of ICMP errors due to a defective or badly configured NAT gateway, router, firewall, or host will be summarily blocked from using this service.
• If you are behind a NAT router or gateway, you should not allow more than a single system on your network to talk to each NTP server. If you have more systems sharing a single IP address, and more than 1 attempt to access this service at roughly the same time, this is likely to be flagged as abuse (excessive query rate) and cause your systems to be automatically blocked for a period of time.
• Extreme cases of abuse will be reported to relevant ISPs and/or law enforcement authorities.
• These rules may be amended at any time, without notice.

Support

iNetStat.net does not offer support for this service, or for configuring your client systems correctly. See the NTP Public Services Project for all support issues.

Links

• ntp.org: home of the Network Time Protocol project
• The NTP FAQ and HOWTO
• NTP Public Services Project
• NTP Pool Project
• Internet Systems Consortium, Inc.
• Network Time Synchronization Research Project
• Internetworking/NTP Research Laboratory — NTP Development Lab, University of Delaware
• RFC1129 — Internet Time Synchronization: The Network Time Protocol
• RFC1305 — Network Time Protocol (Version 3) Specification, Implementation and Analysis
• RFC4330 — Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI
• Wikipedia: Network Time Protocol
• Usenet: comp.protocols.time.ntp

Google Search

Web www.inetstat.net

Copyright © 2008–2010 iNetStat.net. All rights reserved.

This resource last modified Thursday, 24-Dec-2009 01:59:44 GMT

Apache/2.2.14 (FreeBSD) PHP/5.2.12 with Suhosin-Patch DAV/2 mod_perl/2.0.4 Perl/v5.8.9 Server at ntp.inetstat.net Port 80