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 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 507 +151us[ +50us] +/- 7033us ^+ 2a10-3781-08cc.connected> 2 10 377 644 +247us[ +146us] +/- 7200us ^- ntp-public-2.oma.be 2 9 377 427 +121us[ +21us] +/- 22ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 212 +118us[ +118us] +/- 6516us ^* d54c70bd3.static.telenet> 1 10 377 257 +2692us[+2593us] +/- 7914us ^+ 82-64-171-216.subs.proxa> 1 10 377 638 -1430us[-1531us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 23m -696us[ -853us] +/- 7886us ^- time.fu-berlin.de 1 10 377 230 -239us[ -239us] +/- 69ms ^- ntp1.hetzner.de 2 10 377 530 -165us[ -165us] +/- 20ms ^- ntp2.hetzner.de 2 10 377 500 -151us[ -151us] +/- 13ms ^- ntp3.hetzner.de 2 10 377 623 +107us[ +107us] +/- 28ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1026 -240us[ -257us] +/- 7903us ^- time.fu-berlin.de 1 10 377 980 -216us[ -216us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 652 -104us[ -104us] +/- 19ms ^- ntp2.hetzner.de 2 9 377 414 -71us[ -71us] +/- 13ms ^- ntp3.hetzner.de 2 9 377 317 +155us[ +155us] +/- 32ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 236 -344us[ -344us] +/- 3612us ^* time1.esa.int 1 10 377 377 -238us[ -334us] +/- 3611us ^+ ntp1.time.nl 1 10 377 768 -63us[ -152us] +/- 4455us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 845 -177us[ -164us] +/- 7290us ^- time.fu-berlin.de 1 10 377 26m -308us[ -296us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 440 -96us[ -96us] +/- 21ms ^- ntp2.hetzner.de 2 10 377 646 -125us[ -125us] +/- 10ms ^+ ntp3.hetzner.de 2 10 377 710 +138us[ +138us] +/- 27ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 184 -1562us[-1562us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 773 -80us[ -70us] +/- 7410us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 326 -1936us[-1937us] +/- 9523us ^- time.fu-berlin.de 1 10 377 273 -552us[ -552us] +/- 69ms ^- ntp1.hetzner.de 2 8 377 71 -349us[ -349us] +/- 27ms ^- ntp2.hetzner.de 2 8 377 153 -381us[ -381us] +/- 8993us ^- ntp3.hetzner.de 2 8 377 67 -175us[ -175us] +/- 35ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 358 -1607us[-1577us] +/- 24ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 204 +14us[ +45us] +/- 6922us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 84 -281us[ -567us] +/- 9418us ^+ 2a10-3781-08cc.connected> 2 10 377 578 -358us[ -493us] +/- 9708us ^- ntp-public-2.oma.be 2 9 377 167 -2046us[-2306us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1000 -438us[ -445us] +/- 7016us ^+ d54c70bd3.static.telenet> 1 10 377 33m +4662us[+4036us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 62 +154us[ -138us] +/- 5668us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 410 -110us[ -184us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 977 -1780us[-1849us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 944 -2835us[-2905us] +/- 57ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 229 -962us[-1037us] +/- 7989us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 432 -2349us[-2349us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 269 -1371us[-1371us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 305 +276us[ +276us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 483 -311us[ -837us] +/- 8018us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 20 Aug 10:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 436 -876us[ -889us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 1021 -1619us[-1637us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 548 -1357us[-1371us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 693 -132us[ -147us] +/- 8234us ^+ d54c70bd3.static.telenet> 1 10 377 704 +6211us[+6195us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 123 -3240ns[ -13us] +/- 3837us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 20 Aug 10:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 259 -171us[ -148us] +/- 8507us ^- time.fu-berlin.de 1 10 377 799 -505us[ -484us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 200 -325us[ -325us] +/- 26ms ^- ntp2.hetzner.de 2 8 377 102 -381us[ -381us] +/- 9819us ^- ntp3.hetzner.de 2 9 377 230 -111us[ -111us] +/- 33ms