NTP internet time servers at linocomm.net

You may delay, but time will not.
Benjamin Franklin (1706-1790)

Nederlands

What is this all about?

Time is one of the most important things in modern society. Without time keeping, it would be difficult to arrange meetings, take the bus or train or be on time on a wedding ceremony. Not only humans rely on time. Every computer has an internal clock which is used when time stamping your email and documents, schedule your backups and warn you when you have an appointment. Therefore also computers should know the current time with some accuracy. To synchronize computers to known good time sources over the internet, the NTP protocol has been defined which allows to obtain the current time from internet time servers.

The servers ntp1.linocomm.net to ntp9.linocomm.net are such public internet time servers, operated by the internet services company Linoplan. The servers provide NTP services to NTP and SNTP clients on the internet. All time servers are at least stratum 2 servers, which means that the servers are directly connected to other time servers which take their time from a number of official reference clocks (atomic clock, radio clock, GPS or whatever) in different geographical regions. Time server ntp4.linocomm.net is a Stratum 1 server located in the Netherlands with its own reference clock. Time synchronisation with several upstream servers in different geographical regions gives redundancy when network failures occur. In practice this means that the time these servers provide are accurate within a few milliseconds. This is good enough for most private and commercial applications.

Server ntp1.linocomm.net is located in a data center in Almaty, Kazakhstan, which makes it the ideal time server for computers in Central Asia, but clients from all over the world are allowed to connect to this server. The only drawback is that distant clients might observe a few more milliseconds error in the received time signal compared to the time served by time servers closer to their location. Time server ntp5.linocomm.net is located in Las Vegas and serves North America. All other servers are located in Western Europe and are primarily intended for the EMEA area. Time server ntp4 is the most accurate in the network because it has its own timebase with a GPS+PPS receiver.

How do I connect to your time servers?

You can add one or more of the server names to your ntpd or chronyd configuration file. With recent versions of ntpd and chronyd you can use the pool directive which adds a pool of servers to the configuration. If you use the pool directive, use the name ntppool.linocomm.net as the domain name.

How well do your time servers perform?

The lists of upstream servers are refreshed every five minutes. The values in the columns delay, offset and jitter are in milliseconds. The delay is a measurement of the network delay when retrieving the time from the remote server. The offset is the current difference between the internal clock of our timeserver and the remote clock. Finally jitter gives the variation in the time difference between subsequent requests.

Current performance for ntp1.linocomm.net (Almaty, KZ)

NTP1 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp.nic.kz                    1  10   377   355   -145us[ -174us] +/-   11ms
^- n32-6.timepool-1a.d6.hsd>     2  10   352   35m  -1797us[-1876us] +/-  184ms

Current performance for ntp2.linocomm.net (Roubaix, FR)

NTP2 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   901    -71us[  -80us] +/- 3392us
^+ ntp0.rrze.uni-erlangen.de     1   9   377   515    -44us[  -44us] +/- 7280us

Current perfomance for ntp3.linocomm.net (Falkenstein, DE)

NTP3 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   646    -56us[  -26us] +/- 8082us
^- time.fu-berlin.de             1  10   377    92    -78us[  -78us] +/-   58ms
^- ntp1.hetzner.de               2  10   377   766    -66us[  -36us] +/-   17ms
^- ntp2.hetzner.de               2  10   377   250    -37us[  -37us] +/-   19ms
^- ntp3.hetzner.de               2  10   377   978    +58us[  +87us] +/-   43ms

Current performance for ntp4.linocomm.net (Donkerbroek, NL)

NTP4 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp0.nl.uu.net                1  10   377    91   -225us[ -247us] +/- 5215us
^+ time1.esa.int                 1  10   377   854  +2464ns[  -19us] +/- 5099us
^+ ntp1.time.nl                  1  10   377   527   -106us[ -128us] +/- 5884us

Current performance for ntp5.linocomm.net (Naaldwijk, NL)

NTP5 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   912   +226us[ +203us] +/- 1599us
^* time1.esa.int                 1  10   377   150   -105us[ -128us] +/- 1520us
^+ ntp1.time.nl                  1  10   377   806   -197us[ -220us] +/- 2759us

Current perfomance for ntp6.linocomm.net (Gravelines, FR)

NTP6 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   127   -120us[ -155us] +/- 3148us
^+ ntp0.rrze.uni-erlangen.de     1  10   377   201    -61us[  -96us] +/- 7293us

Current performance for ntp7.linocomm.net (Falkenstein, DE)

NTP7 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   875    -85us[ -223us] +/- 8189us
^- time.fu-berlin.de             1  10   377   711   -266us[ -266us] +/-   58ms
^+ ntp1.hetzner.de               2  10   377   304   -164us[ -164us] +/-   24ms
^- ntp2.hetzner.de               2   9   377   231   -162us[ -162us] +/-   19ms
^- ntp3.hetzner.de               2  10   377   764    -52us[  -52us] +/-   24ms

Current perfomance for ntp8.linocomm.net (Roubaix, FR)

NTP8 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntp-main-1.oma.be             1  10   377   955  -1013us[-1030us] +/- 5243us
^+ ntp0.rrze.uni-erlangen.de     1  10   377   427  +1340us[+1340us] +/- 7014us

Current performance for ntp9.linocomm.net (Nürnberg, DE)

NTP9 error 
Wed  9 Oct 13:37:01 UTC 2024
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   26m    -92us[ -117us] +/- 7284us
^- time.fu-berlin.de             1  10   377  1012   -206us[ -206us] +/-   58ms
^- ntp1.hetzner.de               2  10   377   238    -22us[  -22us] +/-   24ms
^- ntp2.hetzner.de               2  10   377   480    -39us[  -39us] +/-   27ms
^- ntp3.hetzner.de               2  10   377   806  -1281us[-1281us] +/-   26ms