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)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 555 +415us[ +415us] +/- 6474us ^* 2a10-3781-08Cc.connected> 2 10 377 750 +291us[ +303us] +/- 6594us ^- ntp-public-2.oma.be 2 9 377 157 -22us[ -22us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 277 -4304us[-4304us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 240 +4356us[+4356us] +/- 10ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 609 +2064us[+2064us] +/- 11ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 880 -118us[ -69us] +/- 7646us ^- time.fu-berlin.de 1 10 377 835 -349us[ -349us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 908 +82us[ +131us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 192 -9870ns[-9870ns] +/- 33ms ^- ntp3.hetzner.de 2 10 377 166 +57us[ +57us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 149 -151us[ -139us] +/- 7895us ^- time.fu-berlin.de 1 10 377 388 -358us[ -348us] +/- 63ms ^+ ntp1.hetzner.de 2 9 377 559 -172us[ -164us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 27m -266us[ -241us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 924 -208us[ -203us] +/- 27ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 234 -625us[ -625us] +/- 3828us ^* time1.esa.int 1 10 377 1011 -496us[ -553us] +/- 3780us ^+ ntp1.time.nl 1 10 377 494 -414us[ -414us] +/- 4569us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 893 -913us[ -930us] +/- 8061us ^- time.fu-berlin.de 1 10 377 673 -586us[ -586us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 957 -145us[ -162us] +/- 26ms ^- ntp2.hetzner.de 2 10 377 86 -1623us[-1623us] +/- 36ms ^- ntp3.hetzner.de 2 10 377 134 -27us[ -27us] +/- 35ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 9 377 514 -1211us[-1214us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 410 +607us[ +605us] +/- 9506us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 42 -70us[ -57us] +/- 7924us ^- time.fu-berlin.de 1 10 377 615 -182us[ -169us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 431 -40us[ -27us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 325 -93us[ -80us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 780 +79us[ +92us] +/- 28ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 144 -2134us[-2134us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 249 -173us[ -653us] +/- 7037us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 10 Jun 06:58:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 247 -169us[ -176us] +/- 7889us ^- time.fu-berlin.de 1 10 377 318 -208us[ -215us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 41 -130us[ -130us] +/- 22ms ^- ntp2.hetzner.de 2 9 377 73 -194us[ -194us] +/- 34ms ^- ntp3.hetzner.de 2 9 377 216 +32us[ +32us] +/- 33ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 10 Jun 06:58:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 447 -382us[ -562us] +/- 9156us ^+ 2A10-3781-08CC.connected> 2 10 377 402 -263us[ -443us] +/- 9316us ^- ntp-public-2.oma.be 2 10 377 793 -2610us[-2787us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 384 -1496us[-1677us] +/- 8125us ^+ d54c70bd3.static.telenet> 1 10 377 290 +3987us[+3987us] +/- 9062us ^+ 82-64-45-50.subs.proxad.> 1 10 377 97 -206us[ -206us] +/- 7655us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 10 Jun 06:58:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 756 -207us[ -207us] +/- 11ms ^+ 2A10-3781-08cC.connected> 2 10 377 690 +107us[ +107us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 221 -429us[ -429us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 848 +340us[ +316us] +/- 8004us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 10 Jun 06:58:08 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 679 +364us[ +364us] +/- 14ms ^? 2a10-3781-08cC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 993 +139us[ +110us] +/- 59ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 779 +379us[ +349us] +/- 8021us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 10 Jun 06:58:08 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 617 -443us[ -435us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 796 -2537us[-2529us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 964 -827us[ -818us] +/- 23ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 204 -607us[ -607us] +/- 7812us ^+ d54c70bd3.static.telenet> 1 10 377 531 +4501us[+4509us] +/- 12ms ^* 82-64-45-50.subs.proxad.> 1 10 377 388 -187us[ -179us] +/- 5423us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 10 Jun 06:58:08 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 846 -548us[ -548us] +/- 8313us ^- time.fu-berlin.de 1 10 377 965 -507us[ -507us] +/- 70ms ^- ntp1.hetzner.de 2 8 377 60 -412us[ -412us] +/- 21ms ^- ntp2.hetzner.de 2 9 377 369 -470us[ -470us] +/- 29ms ^- ntp3.hetzner.de 2 8 377 91 -290us[ -290us] +/- 35ms