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)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 25 +177ns[ +177ns] +/- 7203us ^* 2A10-3781-08Cc.connected> 2 10 377 481 -41us[ -284us] +/- 7120us ^- ntp-public-2.oma.be 2 10 377 526 -358us[ -600us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 119 -4102us[-4102us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 166 +4827us[+4827us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 572 +410us[ +167us] +/- 13ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 347 -336us[ -276us] +/- 7888us ^- time.fu-berlin.de 1 10 377 551 -432us[ -373us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 346 -157us[ -157us] +/- 26ms ^- ntp2.hetzner.de 2 7 377 104 -776us[ -776us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 26m -122us[ -86us] +/- 28ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 830 -2219us[-2255us] +/- 9943us ^- time.fu-berlin.de 1 10 377 783 -1422us[-1422us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 224 -245us[ -245us] +/- 29ms ^- ntp2.hetzner.de 2 8 377 577 -1052us[-1052us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 324 -444us[ -444us] +/- 33ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 816 -640us[-1056us] +/- 3780us ^* time1.esa.int 1 10 377 802 -484us[ -901us] +/- 3731us ^+ ntp1.time.nl 1 10 377 667 -260us[ -260us] +/- 4313us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 706 -2829us[-2809us] +/- 9999us ^- time.fu-berlin.de 1 9 377 55 -333us[ -333us] +/- 66ms ^- ntp1.hetzner.de 2 8 377 23 +6888ns[+6888ns] +/- 31ms ^- ntp2.hetzner.de 2 8 377 32 -569us[ -569us] +/- 24ms ^+ ntp3.hetzner.de 2 7 377 61 -147us[ -147us] +/- 23ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 912 -1733us[-1732us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 344 -20us[ -19us] +/- 7157us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 117 -383us[ -436us] +/- 8003us ^- time.fu-berlin.de 1 10 377 692 -378us[ -428us] +/- 72ms ^- ntp1.hetzner.de 2 7 377 48 -172us[ -172us] +/- 31ms ^- ntp2.hetzner.de 2 8 377 182 -1002us[-1055us] +/- 32ms ^+ ntp3.hetzner.de 2 10 377 24 -413us[ -413us] +/- 22ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 21 Jun 17:01:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 593 -1849us[-1881us] +/- 39ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 440 -144us[ -176us] +/- 8928us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sun 21 Jun 17:01:03 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 21 Jun 17:01:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1017 +55us[ +78us] +/- 9563us ^+ 2a10-3781-08CC.connected> 2 9 377 423 -151us[ -128us] +/- 9363us ^- ntp-public-2.oma.be 2 9 377 203 -2120us[-2120us] +/- 45ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 532 -307us[ -284us] +/- 9004us ^+ d54c70bd3.static.telenet> 1 10 377 645 +4375us[+4398us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 10 377 387 -225us[ -202us] +/- 7591us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 21 Jun 17:01:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 875 -1298us[-1321us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 915 +349us[ +364us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 840 +888us[ +864us] +/- 41ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 367 -85us[ -109us] +/- 8188us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 21 Jun 17:01:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 838 -87us[ -87us] +/- 12ms ^+ 2A10-3781-08cc.connected> 2 10 377 174 -1977us[-1977us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 176 -1812us[-1812us] +/- 51ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 852 -155us[ -115us] +/- 8139us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 21 Jun 17:01:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 183 -698us[ -698us] +/- 12ms ^? 2A10-3781-08Cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 313 -1053us[-1053us] +/- 47ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 328 -982us[ -982us] +/- 7795us ^+ d54c70bd3.static.telenet> 1 10 377 138 +7295us[+7295us] +/- 14ms ^* 82-64-45-50.subs.proxad.> 1 10 377 1185 -183us[ -262us] +/- 5721us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 21 Jun 17:01:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 320 -42us[ -44us] +/- 7954us ^- time.fu-berlin.de 1 9 377 388 -140us[ -142us] +/- 62ms ^- ntp1.hetzner.de 2 7 377 7 +135us[ +135us] +/- 32ms ^- ntp2.hetzner.de 2 7 377 42 -583us[ -583us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 194 -108us[ -108us] +/- 20ms