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)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 493 -80us[ -80us] +/- 6163us ^+ 2a10-3781-08cc.connected> 2 10 377 548 +199us[ +199us] +/- 6316us ^- ntp-public-2.oma.be 2 8 377 235 -193us[ -193us] +/- 18ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 337 -4007us[-4007us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 22m +3915us[+3713us] +/- 9470us ^+ 82-64-171-216.subs.proxa> 1 10 377 37 -675us[ -675us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 30m -1066us[-1127us] +/- 7993us ^- time.fu-berlin.de 1 10 377 226 -218us[ -218us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 260 +458us[ +458us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 59 +14us[ +14us] +/- 14ms ^+ ntp3.hetzner.de 2 10 377 20m -157us[ -157us] +/- 23ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 1119 -1932us[-1814us] +/- 9663us ^- time.fu-berlin.de 1 10 377 560 -498us[ -498us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 35 -1526us[-1526us] +/- 23ms ^- ntp2.hetzner.de 2 10 377 27m -188us[ -83us] +/- 18ms ^- ntp3.hetzner.de 2 8 377 236 -444us[ -444us] +/- 38ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 384 -615us[ -685us] +/- 3785us ^+ time1.esa.int 1 9 377 27 -369us[ -369us] +/- 3438us ^+ ntp1.time.nl 1 9 377 280 -451us[ -451us] +/- 4544us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 373 394 -188us[ -19us] +/- 7336us ^- time.fu-berlin.de 1 10 377 579 -320us[ -158us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 258 +445us[ +445us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 1015 -154us[-4440ns] +/- 11ms ^- ntp3.hetzner.de 2 10 377 68 -36us[ -36us] +/- 41ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 692 -2379us[-2514us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 219 -122us[ -287us] +/- 7165us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 518 -447us[ -516us] +/- 8020us ^- time.fu-berlin.de 1 10 377 380 -532us[ -532us] +/- 71ms ^- ntp1.hetzner.de 2 8 377 225 +186us[ +186us] +/- 18ms ^- ntp2.hetzner.de 2 9 377 157 -297us[ -297us] +/- 11ms ^- ntp3.hetzner.de 2 9 377 181 -403us[ -403us] +/- 38ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 51 -3048us[-3048us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 320 +102us[ +178us] +/- 6892us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 313 -352us[ -272us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 322 -529us[ -450us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 369 -3658us[-3584us] +/- 18ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 493 -625us[ -561us] +/- 6884us ^+ d54c70bd3.static.telenet> 1 10 377 13 +9964us[+9964us] +/- 15ms ^* 82-64-171-216.subs.proxa> 1 10 377 166 -601us[ -509us] +/- 5901us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 626 -2010us[-2364us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 18 -609us[ -609us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 963 -891us[-1236us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 502 -799us[-1156us] +/- 7866us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 655 -439us[ -763us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 102 -2846us[-2876us] +/- 13ms ^+ ntp-public-2.oma.be 2 10 377 416 -1750us[-1861us] +/- 48ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 5 -975us[-1004us] +/- 8144us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 8 Aug 09:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 44 -1036us[-1036us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 301 -971us[-1509us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 87 -1627us[-1627us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 837 -761us[-1295us] +/- 7922us ^+ d54c70bd3.static.telenet> 1 10 377 686 +5626us[+5091us] +/- 14ms ^* 82-64-171-216.subs.proxa> 1 10 377 218 -956us[-1494us] +/- 3979us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 8 Aug 09:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 436 -157us[ -151us] +/- 8294us ^- time.fu-berlin.de 1 10 377 64 -177us[ -177us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 328 +559us[ +559us] +/- 17ms ^- ntp2.hetzner.de 2 8 377 47 +41us[ +41us] +/- 13ms ^- ntp3.hetzner.de 2 9 377 345 -54us[ -54us] +/- 36ms