NTP internet time servers at linocomm.net
You may delay, but time will not.Benjamin Franklin (1706-1790)
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)
Tue 25 Aug 04:37:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 55 -551us[ -551us] +/- 6561us ^+ 2a10-3781-08cc.connected> 2 10 377 955 -256us[ -181us] +/- 6509us ^- ntp-public-2.oma.be 2 10 377 430 -391us[ -391us] +/- 20ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 650 -54us[ +25us] +/- 6573us ^+ d54c70bd3.static.telenet> 1 10 377 395 +3946us[+3946us] +/- 9194us ^+ 82-64-171-216.subs.proxa> 1 10 377 997 +1408us[+1483us] +/- 9196us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 373 376 -100us[ +114us] +/- 6826us ^- time.fu-berlin.de 1 10 377 380 -736us[ -521us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 1052 -554us[ -340us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 444 -520us[ -306us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 692 -2542us[-2327us] +/- 36ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 249 -1226us[-1208us] +/- 7437us ^- time.fu-berlin.de 1 10 377 143 -1819us[-1819us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 853 -1726us[-1709us] +/- 30ms ^- ntp2.hetzner.de 2 9 377 295 -1651us[-1633us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 386 -1657us[-1639us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 420 -171us[+2564ns] +/- 3555us ^* time1.esa.int 1 10 377 302 -56us[ +130us] +/- 3453us ^+ ntp1.time.nl 1 10 377 515 +243us[ +407us] +/- 4177us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 333 1014 -34us[ +64us] +/- 7066us ^- time.fu-berlin.de 1 10 377 915 -342us[ -342us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 978 -147us[ -147us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 1005 -216us[ -216us] +/- 18ms ^- ntp3.hetzner.de 2 10 377 435 -123us[ -123us] +/- 38ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 208 -1408us[-1382us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 82 +540us[ +567us] +/- 7172us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 184 -518us[ -557us] +/- 7767us ^- time.fu-berlin.de 1 10 377 78 -556us[ -556us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 178 -443us[ -443us] +/- 40ms ^- ntp2.hetzner.de 2 10 377 154 -411us[ -411us] +/- 21ms ^- ntp3.hetzner.de 2 10 377 916 -397us[ -434us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 254 -3089us[-3089us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 316 -32us[ -61us] +/- 7008us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 91 -548us[ -548us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 30 -798us[ -798us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 816 -3555us[-3555us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 62 -410us[ -410us] +/- 6955us ^+ d54c70bd3.static.telenet> 1 10 377 20 +3427us[+3427us] +/- 8531us ^* 82-64-171-216.subs.proxa> 1 10 377 969 -410us[ -388us] +/- 5014us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 346 -189ns[ -189ns] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 465 -2696us[-2696us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 249 +148us[ +148us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 606 +194us[ +142us] +/- 8138us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 635 +245us[ +329us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 528 -148us[ -63us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 558 -2063us[-1979us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 346 +295us[ +379us] +/- 8015us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 737 -2854us[-2854us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 6 -952us[ -952us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 170 -1120us[-1120us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 370 -615us[ -615us] +/- 8095us ^+ d54c70bd3.static.telenet> 1 10 377 463 +5835us[+5835us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 837 -319us[ -327us] +/- 3846us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 25 Aug 04:37:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 221 -894us[ -883us] +/- 8617us ^- time.fu-berlin.de 1 10 377 905 -400us[ -388us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 655 -300us[ -289us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 974 -309us[ -297us] +/- 17ms ^- ntp3.hetzner.de 2 9 377 137 -210us[ -210us] +/- 41ms