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 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 654 -479us[ -479us] +/- 6780us ^+ 2a10-3781-08cc.connected> 2 10 377 724 -455us[ -455us] +/- 6453us ^- ntp-public-2.oma.be 2 8 377 194 -115us[ -115us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 42m -120us[ -79us] +/- 6726us ^+ d54c70bd3.static.telenet> 1 10 377 61 +5062us[+5062us] +/- 11ms ^+ 82-64-171-216.subs.proxa> 1 10 377 510 -252us[ -252us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 920 -2548us[-2551us] +/- 9462us ^- time.fu-berlin.de 1 10 377 1023 -619us[ -623us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 558 -233us[ -233us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 523 -2472us[-2472us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 848 -2858us[-2858us] +/- 53ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 476 +28us[ +531us] +/- 6918us ^- time.fu-berlin.de 1 10 377 971 -1089us[ -590us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 296 -593us[ -593us] +/- 38ms ^- ntp2.hetzner.de 2 7 377 37 -2722us[-2722us] +/- 31ms ^- ntp3.hetzner.de 2 8 377 52 -1577us[-1577us] +/- 29ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 274 -169us[ -158us] +/- 3729us ^+ time1.esa.int 1 10 377 951 -278us[ -268us] +/- 3714us ^+ ntp1.time.nl 1 10 377 419 -280us[ -269us] +/- 4646us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 34m -1842us[-1837us] +/- 9211us ^- time.fu-berlin.de 1 10 377 552 -279us[ -279us] +/- 72ms ^- ntp1.hetzner.de 2 9 377 373 +68us[ +68us] +/- 36ms ^- ntp2.hetzner.de 2 9 377 44 -1728us[-1728us] +/- 32ms ^- ntp3.hetzner.de 2 9 377 320 -812us[ -812us] +/- 27ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 352 -1423us[-1383us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 93 +14us[ +58us] +/- 7137us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 0 -1340us[-1391us] +/- 8948us ^- time.fu-berlin.de 1 10 377 194 -483us[ -533us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 136 +27us[ -23us] +/- 40ms ^- ntp2.hetzner.de 2 7 377 53 -2130us[-2181us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 80 -986us[-1037us] +/- 29ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 279 -1401us[-1388us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 206 -6811ns[+7852ns] +/- 7087us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 610 +207us[ +207us] +/- 9356us ^+ 2a10-3781-08cc.connected> 2 10 377 867 +530us[ +650us] +/- 9515us ^- ntp-public-2.oma.be 2 10 377 440 -1126us[-1126us] +/- 35ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 795 +216us[ +216us] +/- 6898us ^+ d54c70bd3.static.telenet> 1 10 377 726 +4250us[+4250us] +/- 8588us ^* 82-64-171-216.subs.proxa> 1 10 377 850 +420us[ +540us] +/- 5574us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 29 Aug 19:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 963 -1898us[-1814us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 129 -1496us[-1496us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 434 +489us[ +489us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 866 +393us[ +478us] +/- 8180us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 29 Aug 19:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 275 -36us[ -834us] +/- 10ms ^+ 2a10-3781-08cc.connected> 2 10 377 269 +22us[ -777us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 203 +493us[ +493us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 213 +414us[ -387us] +/- 8169us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 29 Aug 19:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 492 -349us[ -196us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 656 -1523us[-1377us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 574 +436us[ +585us] +/- 36ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 198 +545us[ +708us] +/- 8159us ^- d54c70bd3.static.telenet> 1 10 377 301 +3647us[+3807us] +/- 9375us ^* 82-64-171-216.subs.proxa> 1 10 377 147 +415us[ +581us] +/- 3846us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 29 Aug 19:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 980 -38us[ +22us] +/- 7492us ^- time.fu-berlin.de 1 9 377 231 -499us[ -499us] +/- 62ms ^- ntp1.hetzner.de 2 7 377 115 +39us[ +39us] +/- 40ms ^- ntp2.hetzner.de 2 6 377 53 -2071us[-2071us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 149 -937us[ -937us] +/- 29ms