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 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 854 +43us[+4475ns] +/- 7417us ^+ 2a10-3781-08cc.connected> 2 10 377 936 +196us[ +158us] +/- 7201us ^- ntp-public-2.oma.be 2 8 377 99 +755us[ +755us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 702 -3839us[-3839us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 774 +3496us[+3496us] +/- 8563us ^+ 82-64-171-216.subs.proxa> 1 10 377 601 -1427us[-1427us] +/- 9961us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 223 +264us[ +267us] +/- 8881us ^- time.fu-berlin.de 1 10 377 810 -264us[ -263us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 177 -159us[ -159us] +/- 26ms ^- ntp2.hetzner.de 2 9 377 27 -969us[ -969us] +/- 45ms ^- ntp3.hetzner.de 2 10 377 898 +108us[ +109us] +/- 19ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 363 541 -769us[ -652us] +/- 10ms ^- time.fu-berlin.de 1 10 377 428 -1281us[-1281us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 275 -618us[ -618us] +/- 26ms ^- ntp2.hetzner.de 2 8 377 77 -1250us[-1250us] +/- 43ms ^- ntp3.hetzner.de 2 8 377 112 -312us[ -312us] +/- 20ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 837 +325us[ +450us] +/- 3206us ^+ time1.esa.int 1 10 377 121 +278us[ +278us] +/- 3381us ^+ ntp1.time.nl 1 10 377 911 -418us[ -297us] +/- 4988us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 29m -341us[ -323us] +/- 7348us ^- time.fu-berlin.de 1 10 377 33m -352us[ -334us] +/- 57ms ^- ntp1.hetzner.de 2 10 377 70 -2872us[-2872us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 110 -1067us[-1067us] +/- 44ms ^- ntp3.hetzner.de 2 10 377 949 -92us[ -92us] +/- 18ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 6 Aug 19:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 271 -1153us[-1153us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 605 +363us[ +301us] +/- 9316us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 32m -256us[ -262us] +/- 7823us ^- time.fu-berlin.de 1 10 377 30m -246us[ -246us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 602 -404us[ -404us] +/- 34ms ^- ntp2.hetzner.de 2 6 377 59 -1106us[-1106us] +/- 43ms ^- ntp3.hetzner.de 2 6 377 48 -127us[ -127us] +/- 21ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 152 -2078us[-2078us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 938 -655us[ -714us] +/- 8080us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 120 -478us[ -478us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 178 -506us[ -506us] +/- 11ms ^- ntp-public-2.oma.be 2 7 377 86 -2467us[-2467us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 429 -1027us[-1027us] +/- 8022us ^+ d54c70bd3.static.telenet> 1 10 377 454 +3852us[+3852us] +/- 8858us ^* 82-64-171-216.subs.proxa> 1 10 377 472 +409us[ +178us] +/- 5902us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 992 -2249us[-1993us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 380 +513us[ +869us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 822 -1279us[-1002us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 173 +479us[ +843us] +/- 8155us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 88 -1648us[-1648us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 536 +155us[ +80us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 750 +265us[ +145us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 107 +400us[ +350us] +/- 7920us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 466 -523us[ -163us] +/- 10ms ^+ 2a10-3781-08cc.connected> 2 10 377 669 -2486us[-2126us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 17 +886us[ +886us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 226 +228us[ +590us] +/- 8099us ^+ d54c70bd3.static.telenet> 1 10 377 69 +4300us[+4300us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 123 +360us[ +722us] +/- 3728us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 6 Aug 19:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 32m -639us[ -557us] +/- 8146us ^- time.fu-berlin.de 1 10 377 450 -681us[ -681us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 351 -836us[ -836us] +/- 38ms ^- ntp2.hetzner.de 2 6 377 3 -1531us[-1531us] +/- 44ms ^- ntp3.hetzner.de 2 7 377 61 -539us[ -539us] +/- 21ms