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 (Amsterdam, NL)

NTP1 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   927  +1041us[+1041us] +/- 7599us
^* 2A10-3781-08cC.connected>     2  10   373   123   +309us[ +305us] +/- 6306us
^- ntp-public-2.oma.be           2  10   377   728   +581us[ +580us] +/-   32ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   582  -3613us[-3615us] +/-   11ms
^+ d54c70bd3.static.telenet>     1  10   377   641  +2859us[+2858us] +/- 7744us
^+ 82-64-45-50.subs.proxad.>     1  10   377   972   +953us[ +952us] +/-   10ms

Current performance for ntp2.linocomm.net (Nuremberg, DE)

NTP4 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   20m   -786us[ -736us] +/- 7719us
^- time.fu-berlin.de             1  10   377   102  -1023us[-1023us] +/-   72ms
^- ntp1.hetzner.de               2  10   377   206   -263us[ -263us] +/-   34ms
^- ntp2.hetzner.de               2  10   377   535   -593us[ -593us] +/-   41ms
^- ntp3.hetzner.de               2  10   377    44   -528us[ -528us] +/-   33ms

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

NTP4 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   530  -1274us[-1306us] +/- 8299us
^- time.fu-berlin.de             1  10   377   741  -1407us[-1437us] +/-   63ms
^- ntp1.hetzner.de               2   9   377   125  -1046us[-1046us] +/-   37ms
^- ntp2.hetzner.de               2  10   377   432  -1154us[-1154us] +/-   42ms
^- ntp3.hetzner.de               2  10   377   281  -2184us[-2184us] +/-   29ms

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

NTP4 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp0.nl.uu.net                1  10   377   568    +40us[ -224ns] +/- 3905us
^* time1.esa.int                 1   9   377   319   -142us[ -190us] +/- 3356us
^+ ntp1.time.nl                  1  10   377   855    -86us[ -346us] +/- 4377us

Current performance for ntp5.linocomm.net (Paris, FR)

NTP5 error
Sun  7 Jun 08:34:01 UTC 2026

Current performance for ntp9.linocomm.net (Nuremberg, DE)

NTP9 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   21m   +479us[ +546us] +/- 7782us
^- time.fu-berlin.de             1  10   377  1025   -465us[ -465us] +/-   58ms
^+ ntp1.hetzner.de               2  10   377   244    -51us[  -51us] +/-   34ms
^- ntp2.hetzner.de               2  10   377   454   -253us[ -253us] +/-   43ms
^- ntp3.hetzner.de               2  10   377   980   -197us[ -197us] +/-   44ms

Current performance for ntp16.linocomm.net (Gravelines, FR)

NTP16 error
Wed 10 Jun 17:07:01 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ ntp-public-2.oma.be           2  10   377   324  -1017us[-1298us] +/-   23ms
^* ntp0.rrze.uni-erlangen.de     1  10   377   194   +390us[ +107us] +/- 9309us

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

NTP17 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   363  +4251ns[  +39us] +/- 7859us
^- time.fu-berlin.de             1  10   377   929   -283us[ -249us] +/-   60ms
^+ ntp1.hetzner.de               2  10   377   238    +20us[  +20us] +/-   35ms
^- ntp2.hetzner.de               2   9   377   131    -71us[  -71us] +/-   46ms
^- ntp3.hetzner.de               2  10   377    92   -119us[ -119us] +/-   31ms

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

NTP18 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- ntp-public-2.oma.be           2  10   377   992  -1727us[-1760us] +/-   46ms
^* ntp0.rrze.uni-erlangen.de     1  10   337   627    +23us[  -12us] +/- 9134us

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

NTP20 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   26m   -911us[ -914us] +/- 8326us
^- time.fu-berlin.de             1   9   377   144   -766us[ -766us] +/-   72ms
^- ntp1.hetzner.de               2   9   377   357   -353us[ -353us] +/-   33ms
^- ntp2.hetzner.de               2   9   377   475   -526us[ -526us] +/-   41ms
^- ntp3.hetzner.de               2  10   377   574   -477us[ -477us] +/-   48ms

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

NTP21 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   756   -516us[ -583us] +/- 8513us
^+ 2a10-3781-08cC.connected>     2  10   377   701   -273us[ -339us] +/- 8861us
^- ntp-public-2.oma.be           2  10   377   157  -1984us[-1984us] +/-   25ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   703   -319us[ -385us] +/- 9055us
^* d54c70bd3.static.telenet>     1  10   377   675  +4026us[+3959us] +/-   10ms
^+ 82-64-45-50.subs.proxad.>     1  10   377   469    -60us[  -60us] +/- 7385us

Current performance for ntp22.linocomm.net (Paris, FR)

NTP22 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377    50  -2149us[-2266us] +/-   13ms
^+ 2A10-3781-08cC.connected>     2  10   377  1023    -90us[ -158us] +/-   12ms
^- ntp-public-2.oma.be           2  10   377   571   +181us[ +114us] +/-   39ms
^* ntp0.rrze.uni-erlangen.de     1   9   377    11   -273us[ -390us] +/- 7876us

Current performance for ntp23.linocomm.net (Paris, FR)

NTP23 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377     7  -1111us[-1111us] +/-   13ms
^? 2a10-3781-08Cc.connected>     0  10     0     -     +0ns[   +0ns] +/-    0ns
^- ntp-public-2.oma.be           2  10   377   355    -30us[  +58us] +/-   26ms
^* ntp0.rrze.uni-erlangen.de     1  10   377    74   +140us[ +225us] +/- 7876us

Current performance for ntp24.linocomm.net (Paris, FR)

NTP24 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^+ erquy.linocomm.net            2  10   377   944   -392us[ -402us] +/-   12ms
^+ 2a10-3781-08Cc.connected>     2  10   377    93   -427us[ -427us] +/-   11ms
^- ntp-public-2.oma.be           2  10   377   193   -701us[ -701us] +/-   29ms
^+ ntp0.rrze.uni-erlangen.de     1  10   377   511   -520us[ -520us] +/- 7824us
^+ d54c70bd3.static.telenet>     1  10   377   847  +5071us[+5059us] +/-   12ms
^* 82-64-45-50.subs.proxad.>     1  10   377   724   +245us[ +229us] +/- 5732us

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

NTP25 error
Wed 10 Jun 17:07:02 UTC 2026
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^* ntps1-0.eecsit.tu-berlin>     1  10   377   115   -945us[ -949us] +/- 8667us
^- time.fu-berlin.de             1  10   377   309   -471us[ -475us] +/-   69ms
^- ntp1.hetzner.de               2   9   377   419   -150us[ -153us] +/-   32ms
^- ntp2.hetzner.de               2   9   377    93   -224us[ -224us] +/-   47ms
^- ntp3.hetzner.de               2  10   377   943   -281us[ -284us] +/-   43ms