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 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 174 +411us[ +411us] +/- 6526us ^* 2A10-3781-08cc.connected> 2 10 377 207 +541us[ +442us] +/- 7053us ^- ntp-public-2.oma.be 2 8 377 16 +584us[ +584us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 647 -3092us[-3187us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 40m +6300us[+6113us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 727 -608us[ -703us] +/- 9544us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 25m -126us[ -148us] +/- 7215us ^- time.fu-berlin.de 1 10 377 819 -350us[ -350us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 1 -601us[ -601us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 207 -243us[ -243us] +/- 47ms ^- ntp3.hetzner.de 2 10 377 1037 -1967us[-1967us] +/- 28ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 21m -300us[ -306us] +/- 7958us ^- time.fu-berlin.de 1 9 377 280 -1052us[-1052us] +/- 69ms ^- ntp1.hetzner.de 2 8 377 334 -805us[ -805us] +/- 18ms ^- ntp2.hetzner.de 2 7 377 207 -396us[ -396us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 19 -1991us[-1991us] +/- 30ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 359 -176us[ -142us] +/- 3684us ^* time1.esa.int 1 9 377 183 -2438ns[ +29us] +/- 3625us ^+ ntp1.time.nl 1 9 377 496 -31us[+5038ns] +/- 4572us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 613 -160us[ -105us] +/- 7436us ^- time.fu-berlin.de 1 10 377 152 -1739us[-1739us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 317 -602us[ -602us] +/- 17ms ^- ntp2.hetzner.de 2 9 377 238 -148us[ -148us] +/- 46ms ^- ntp3.hetzner.de 2 10 377 670 -364us[ -309us] +/- 19ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 67 -3124us[-3124us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 919 -61us[ -59us] +/- 7385us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 928 -158us[ -127us] +/- 8005us ^- time.fu-berlin.de 1 10 377 892 -265us[ -265us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 501 -682us[ -682us] +/- 29ms ^- ntp2.hetzner.de 2 7 377 47 -303us[ -303us] +/- 48ms ^- ntp3.hetzner.de 2 10 377 329 -370us[ -370us] +/- 24ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 508 -2854us[-2872us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 121 +8877ns[-8348ns] +/- 7004us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 16 Jul 19:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 860 -412us[ -350us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 9 377 191 -96us[ -96us] +/- 12ms ^- ntp-public-2.oma.be 2 8 377 236 -2898us[-2898us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 346 +90us[ +90us] +/- 7092us ^+ d54c70bd3.static.telenet> 1 10 377 783 +2631us[+2692us] +/- 7641us ^* 82-64-171-216.subs.proxa> 1 10 377 719 +102us[ +162us] +/- 5651us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 16 Jul 19:31:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 128 +1332us[+1278us] +/- 13ms ^+ 2A10-3781-08cc.connected> 2 10 377 582 -2093us[-2149us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 637 +1699us[+1642us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 97 +274us[ +220us] +/- 7919us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 16 Jul 19:31:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 587 +65us[ +56us] +/- 11ms ^+ 2a10-3781-08CC.connected> 2 10 377 345 -1769us[-1777us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 355 +1614us[+1606us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 77 +668us[ +660us] +/- 8013us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 16 Jul 19:31:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 794 -197us[ -160us] +/- 15ms ^- 2A10-3781-08CC.connected> 2 10 377 985 -2066us[-2030us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 945 -82us[ -46us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 743 +361us[ +398us] +/- 8070us ^- d54c70bd3.static.telenet> 1 10 377 857 +6326us[+6362us] +/- 14ms ^* 82-64-171-216.subs.proxa> 1 10 377 717 +444us[ +481us] +/- 3863us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 16 Jul 19:31:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 921 -282us[ -302us] +/- 7939us ^- time.fu-berlin.de 1 9 377 96 -213us[ -213us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 499 -682us[ -682us] +/- 29ms ^- ntp2.hetzner.de 2 7 377 84 -264us[ -264us] +/- 47ms ^- ntp3.hetzner.de 2 10 377 458 -307us[ -307us] +/- 22ms