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 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 658 +403us[ +369us] +/- 6707us ^* 2a10-3781-08cc.connected> 2 10 377 167 +391us[ +356us] +/- 6169us ^- ntp-public-2.oma.be 2 9 377 454 +468us[ +433us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 293 -3562us[-3598us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 733 +6646us[+6612us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 922 +1025us[ +991us] +/- 8918us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 704 -360us[ -360us] +/- 7450us ^- time.fu-berlin.de 1 10 377 518 -405us[ -405us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 296 -486us[ -486us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 438 -1308us[-1308us] +/- 35ms ^- ntp3.hetzner.de 2 9 377 124 -768us[ -768us] +/- 26ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 934 -805us[ -797us] +/- 8909us ^- time.fu-berlin.de 1 9 377 294 -261us[ -261us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 822 -333us[ -333us] +/- 45ms ^- ntp2.hetzner.de 2 9 377 136 -1217us[-1217us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 852 -457us[ -457us] +/- 30ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 264 +302us[ +336us] +/- 3720us ^* time1.esa.int 1 10 377 185 -126us[ -92us] +/- 3437us ^+ ntp1.time.nl 1 9 377 43 -187us[ -187us] +/- 4366us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 500 -279us[ -301us] +/- 7290us ^- time.fu-berlin.de 1 10 377 31m -2222us[-2300us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 710 -754us[ -776us] +/- 45ms ^- ntp2.hetzner.de 2 10 377 740 -1472us[-1494us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 106 -728us[ -728us] +/- 26ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 107 -1533us[-1533us] +/- 41ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 187 +3ns[-1070ns] +/- 7191us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 615 -1596us[-1619us] +/- 9222us ^- time.fu-berlin.de 1 10 377 946 -468us[ -491us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 792 -559us[ -582us] +/- 45ms ^- ntp2.hetzner.de 2 7 377 74 -1551us[-1551us] +/- 23ms ^- ntp3.hetzner.de 2 9 377 297 -715us[ -715us] +/- 38ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 826 -1678us[-1765us] +/- 30ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 14 -90us[ -142us] +/- 6903us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Tue 28 Jul 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 286 +1519ns[+1519ns] +/- 9349us ^+ 2a10-3781-08cc.connected> 2 9 377 88 +105us[ +105us] +/- 8648us ^- ntp-public-2.oma.be 2 10 377 826 -1699us[-1699us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 204 +91us[ +91us] +/- 6900us ^+ d54c70bd3.static.telenet> 1 10 377 597 +3615us[+3615us] +/- 9020us ^* 82-64-171-216.subs.proxa> 1 10 377 840 -18us[ +52us] +/- 5739us
Current performance for ntp22.linocomm.net (Paris, FR)
Tue 28 Jul 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 725 -389us[ -364us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 647 -1826us[-1800us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 14 +303us[ +303us] +/- 47ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 96 +418us[ +448us] +/- 8065us
Current performance for ntp23.linocomm.net (Paris, FR)
Tue 28 Jul 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 120 +393us[ +492us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 795 -47us[ +156us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 204 -1078us[ -952us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 45 +216us[ +312us] +/- 7843us
Current performance for ntp24.linocomm.net (Paris, FR)
Tue 28 Jul 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 123 +1833us[+1917us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 113 -1606us[-1606us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 122 +357us[ +440us] +/- 45ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 189 +343us[ +424us] +/- 7824us ^- d54c70bd3.static.telenet> 1 10 377 193 +2390us[+2471us] +/- 8588us ^* 82-64-171-216.subs.proxa> 1 10 377 119 +986us[+1069us] +/- 3992us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Tue 28 Jul 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 29m -1138us[-1107us] +/- 9301us ^- time.fu-berlin.de 1 9 377 35 +442us[ +442us] +/- 61ms ^- ntp1.hetzner.de 2 7 377 68 +364us[ +364us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 391 -535us[ -535us] +/- 34ms ^- ntp3.hetzner.de 2 9 377 100 +149us[ +149us] +/- 24ms