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)
Sat 27 Jun 19:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 83 +201us[ +201us] +/- 6756us ^* 2a10-3781-08Cc.connected> 2 10 377 186 +43us[ +77us] +/- 6815us ^- ntp-public-2.oma.be 2 8 377 21 +939us[ +939us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 728 -3054us[-3021us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 895 +8300us[+8332us] +/- 13ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 360 +1494us[+1527us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 24m -531us[ -522us] +/- 7555us ^- time.fu-berlin.de 1 10 377 853 -440us[ -440us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 225 -801us[ -801us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 189 -306us[ -306us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 863 -691us[ -691us] +/- 30ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 25m -2439us[-2461us] +/- 10ms ^- time.fu-berlin.de 1 10 377 332 -176us[ -176us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 274 -596us[ -596us] +/- 28ms ^- ntp2.hetzner.de 2 10 377 564 -127us[ -127us] +/- 39ms ^- ntp3.hetzner.de 2 9 377 371 -529us[ -529us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 745 +204us[ +204us] +/- 3438us ^* time1.esa.int 1 10 377 777 +213us[ +531us] +/- 3459us ^+ ntp1.time.nl 1 10 377 26m -235us[ +75us] +/- 4635us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1026 -927us[ -954us] +/- 8312us ^- time.fu-berlin.de 1 10 377 804 -734us[ -734us] +/- 61ms ^- ntp1.hetzner.de 2 8 377 20 -746us[ -746us] +/- 24ms ^- ntp2.hetzner.de 2 8 377 445 -356us[ -356us] +/- 42ms ^- ntp3.hetzner.de 2 9 377 148 -788us[ -788us] +/- 41ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 35 -1692us[-1692us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 89 -58us[ -73us] +/- 7331us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 355 1015 -107us[ +50us] +/- 7452us ^- time.fu-berlin.de 1 10 373 668 -466us[ -466us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 137 -873us[ -873us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 568 -386us[ -386us] +/- 38ms ^- ntp3.hetzner.de 2 9 377 151 -798us[ -798us] +/- 40ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 27 Jun 19:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 513 -2228us[-1843us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 382 -623us[ -225us] +/- 9004us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sat 27 Jun 19:46:03 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 27 Jun 19:46:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 947 -1432us[-1203us] +/- 11ms ^+ 2a10-3781-08CC.connected> 2 10 377 739 +786us[+1016us] +/- 9726us ^- ntp-public-2.oma.be 2 8 377 73 -1231us[-1231us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 559 +33us[ +33us] +/- 9022us ^+ d54c70bd3.static.telenet> 1 10 377 404 +3943us[+3943us] +/- 9008us ^* 82-64-45-50.subs.proxad.> 1 10 377 657 +590us[ +820us] +/- 7659us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 27 Jun 19:46:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 571 +91us[ +91us] +/- 12ms ^+ 2A10-3781-08Cc.connected> 2 10 377 705 +19us[ +19us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 470 +596us[ +596us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 908 +370us[ +348us] +/- 7928us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 27 Jun 19:46:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 797 -849us[ -771us] +/- 15ms ^+ 2a10-3781-08CC.connected> 2 10 377 597 +240us[ +317us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 842 +1868us[+1947us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 113 +591us[ +667us] +/- 7884us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 27 Jun 19:46:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 776 +385us[ +442us] +/- 12ms ^? 2a10-3781-08cC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 958 -574us[ -517us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 155 -468us[ -468us] +/- 7992us ^+ d54c70bd3.static.telenet> 1 10 377 32m +4389us[+4324us] +/- 12ms ^* 82-64-45-50.subs.proxad.> 1 10 377 516 +130us[ +188us] +/- 5776us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 27 Jun 19:46:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 47 -545us[ -542us] +/- 7820us ^- time.fu-berlin.de 1 10 377 879 -639us[ -635us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 472 -911us[ -907us] +/- 25ms ^- ntp2.hetzner.de 2 9 377 270 -406us[ -403us] +/- 32ms ^- ntp3.hetzner.de 2 8 377 62 -821us[ -817us] +/- 41ms