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)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 817 -221us[ -273us] +/- 6707us ^+ 2A10-3781-08Cc.connected> 2 10 377 919 +395us[ +343us] +/- 6974us ^- ntp-public-2.oma.be 2 9 377 168 +509us[ +509us] +/- 42ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 829 -3781us[-3833us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 706 +4126us[+4126us] +/- 10ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 763 +908us[ +908us] +/- 9998us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 147 -163us[ -146us] +/- 7324us ^- time.fu-berlin.de 1 10 377 433 -357us[ -340us] +/- 57ms ^- ntp1.hetzner.de 2 10 377 927 -25us[-8869ns] +/- 19ms ^- ntp2.hetzner.de 2 10 377 3 -145us[ -145us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 454 -450us[ -433us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 740 -1575us[-1591us] +/- 9552us ^- time.fu-berlin.de 1 10 377 578 -350us[ -350us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 905 +159us[ +142us] +/- 20ms ^- ntp2.hetzner.de 2 9 377 421 -115us[ -115us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 837 -380us[ -396us] +/- 41ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 713 +160us[ +160us] +/- 3677us ^* time1.esa.int 1 10 377 20m -144us[ -225us] +/- 3784us ^+ ntp1.time.nl 1 10 377 150 +61us[ +61us] +/- 4625us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 373 673 -259us[ -548us] +/- 7352us ^- time.fu-berlin.de 1 10 377 738 -295us[ -582us] +/- 68ms ^- ntp1.hetzner.de 2 9 377 845 +66us[ -220us] +/- 20ms ^- ntp2.hetzner.de 2 10 377 653 -1906us[-1906us] +/- 19ms ^- ntp3.hetzner.de 2 9 377 285 -311us[ -311us] +/- 38ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 509 -1561us[-1580us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 293 -37us[ -57us] +/- 7312us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 960 -426us[ -449us] +/- 7819us ^- time.fu-berlin.de 1 10 377 126 -553us[ -553us] +/- 62ms ^- ntp1.hetzner.de 2 7 377 11 -148us[ -148us] +/- 27ms ^- ntp2.hetzner.de 2 8 377 123 -377us[ -377us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 62 -586us[ -586us] +/- 40ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 795 -1560us[-1561us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 57 -5190ns[-7171ns] +/- 6976us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 3 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 678 -705us[ -705us] +/- 9341us ^+ 2a10-3781-08Cc.connected> 2 10 377 389 -1064us[-1064us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 632 -1984us[-1984us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 796 -390us[ -354us] +/- 6990us ^+ d54c70bd3.static.telenet> 1 10 377 665 +3253us[+3253us] +/- 9751us ^+ 82-64-45-50.subs.proxad.> 1 10 377 348 -387us[ -387us] +/- 7352us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 3 Jul 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 271 -1746us[-1786us] +/- 14ms ^+ 2A10-3781-08cC.connected> 2 10 377 90 -2395us[-2395us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 790 +454us[ +475us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 162 +426us[ +386us] +/- 8017us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 3 Jul 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 207 +1310us[+1310us] +/- 13ms ^+ 2A10-3781-08Cc.connected> 2 10 377 54 +79us[ +79us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 919 -931us[ -926us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 279 +276us[ +275us] +/- 7935us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 3 Jul 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 29 -2345us[-2345us] +/- 14ms ^+ 2A10-3781-08Cc.connected> 2 9 377 444 -577us[ -497us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 49 +1282us[+1282us] +/- 50ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 249 +85us[ +171us] +/- 8184us ^+ d54c70bd3.static.telenet> 1 10 377 512 +4986us[+5064us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 9 377 99 +195us[ +286us] +/- 5579us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 3 Jul 19:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 845 -71us[ +10us] +/- 8088us ^- time.fu-berlin.de 1 10 377 132 -366us[ -366us] +/- 62ms ^- ntp1.hetzner.de 2 7 377 68 +115us[ +115us] +/- 26ms ^- ntp2.hetzner.de 2 9 377 451 -128us[ -128us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 920 -303us[ -222us] +/- 40ms