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)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 9 377 409 +264us[ +214us] +/- 6733us ^+ 2a10-3781-08cc.connected> 2 10 377 124 +119us[ +119us] +/- 6983us ^- ntp-public-2.oma.be 2 10 377 479 +514us[ +466us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 451 -3647us[-3696us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 341 +7609us[+7609us] +/- 13ms ^+ 82-64-171-216.subs.proxa> 1 10 377 914 +762us[ +714us] +/- 8407us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 482 -56us[-8128ns] +/- 7498us ^- time.fu-berlin.de 1 10 377 259 -206us[ -206us] +/- 58ms ^+ ntp1.hetzner.de 2 10 377 868 -1476us[-1428us] +/- 19ms ^- ntp2.hetzner.de 2 10 377 193 -89us[ -89us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 383 -297us[ -297us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 522 -1679us[-1686us] +/- 9533us ^- time.fu-berlin.de 1 8 377 56 -310us[ -310us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 370 -197us[ -197us] +/- 26ms ^- ntp2.hetzner.de 2 9 377 23 -262us[ -262us] +/- 34ms ^- ntp3.hetzner.de 2 8 377 424 -425us[ -425us] +/- 33ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 9 377 515 +322us[ +414us] +/- 3480us ^+ time1.esa.int 1 10 377 257 -2847us[-2847us] +/- 6416us ^+ ntp1.time.nl 1 8 377 65 +210us[ +210us] +/- 4516us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 967 -89us[ -68us] +/- 7421us ^- time.fu-berlin.de 1 10 377 239 -242us[ -242us] +/- 58ms ^+ ntp1.hetzner.de 2 10 377 162 -25us[ -25us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 347 -1407us[-1407us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 316 -342us[ -342us] +/- 17ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 305 -1516us[-1516us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 435 -124us[ -132us] +/- 7241us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 185 -241us[ -215us] +/- 8087us ^- time.fu-berlin.de 1 10 377 314 -424us[ -398us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 340 -300us[ -273us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 557 -400us[ -374us] +/- 51ms ^- ntp3.hetzner.de 2 8 377 147 -516us[ -516us] +/- 18ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 141 -1604us[-1604us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 973 -128us[ -136us] +/- 7054us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 392 -317us[ -317us] +/- 8979us ^+ 2a10-3781-08cc.connected> 2 8 377 13 -572us[ -572us] +/- 9332us ^- ntp-public-2.oma.be 2 9 377 200 -1623us[-1623us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 20 -160us[ -160us] +/- 6913us ^+ d54c70bd3.static.telenet> 1 10 377 991 +5111us[+4950us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 625 +171us[ +33us] +/- 5832us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 769 +1573us[+1688us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 729 -1925us[-1809us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 348 +602us[ +602us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 619 +575us[ +693us] +/- 8173us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 982 +644us[+1539us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 427 +615us[ +615us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 862 +1195us[+2093us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 578 +1018us[+1925us] +/- 7823us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 23 Jul 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 715 +922us[+1672us] +/- 14ms ^- 2a10-3781-08cc.connected> 2 10 377 766 -2474us[-1732us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 362 +132us[ +931us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 10 277 208 +268us[+1089us] +/- 8093us ^- d54c70bd3.static.telenet> 1 10 377 1038 +3203us[+3906us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 131 +237us[+1069us] +/- 3642us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 23 Jul 19:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 181 -153us[ -61us] +/- 7893us ^- time.fu-berlin.de 1 9 377 285 -308us[ -216us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 497 -200us[ -108us] +/- 24ms ^- ntp2.hetzner.de 2 9 377 243 -279us[ -187us] +/- 30ms ^- ntp3.hetzner.de 2 7 377 20 -413us[ -413us] +/- 20ms