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 20 Jun 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 624 +261us[ +269us] +/- 6427us ^* 2a10-3781-08cc.connected> 2 10 377 51 +121us[ +133us] +/- 6356us ^- ntp-public-2.oma.be 2 10 377 120 +64us[ +76us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 280 -3681us[-3670us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 913 +2614us[+2619us] +/- 8691us ^+ 82-64-45-50.subs.proxad.> 1 10 377 152 +383us[ +395us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 20 Jun 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 32m -41us[ -189us] +/- 7260us ^- time.fu-berlin.de 1 10 377 326 +26us[ +26us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 36 -101us[ -101us] +/- 35ms ^- ntp2.hetzner.de 2 7 377 27 +128us[ +128us] +/- 19ms ^- ntp3.hetzner.de 2 8 377 149 +192us[ +192us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 20 Jun 17:04:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 26m -1354us[-1379us] +/- 9030us ^- time.fu-berlin.de 1 10 377 22m -1176us[-1176us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 121 -708us[ -708us] +/- 34ms ^- ntp2.hetzner.de 2 7 377 122 -551us[ -551us] +/- 17ms ^- ntp3.hetzner.de 2 8 377 206 -385us[ -385us] +/- 33ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 384 -114us[ -202us] +/- 3361us ^* time1.esa.int 1 9 377 126 -233us[ -323us] +/- 3594us ^+ ntp1.time.nl 1 9 377 281 -323us[ -411us] +/- 4364us
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 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 305 -1585us[-1543us] +/- 8937us ^- time.fu-berlin.de 1 9 377 513 -435us[ -397us] +/- 70ms ^- ntp1.hetzner.de 2 8 377 16 -475us[ -475us] +/- 35ms ^- ntp2.hetzner.de 2 8 377 15 -317us[ -317us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 614 -202us[ -165us] +/- 29ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 505 -1613us[-1613us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 548 +13us[ +74us] +/- 7259us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 693 -347us[ -324us] +/- 8007us ^- time.fu-berlin.de 1 10 377 201 -494us[ -494us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 507 -651us[ -651us] +/- 28ms ^- ntp2.hetzner.de 2 7 377 116 -437us[ -437us] +/- 17ms ^- ntp3.hetzner.de 2 8 377 17 -351us[ -351us] +/- 36ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 167 -2009us[-2009us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 568 -334us[ -467us] +/- 8901us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Sat 20 Jun 17:04:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 26 -94us[ -98us] +/- 7972us ^- time.fu-berlin.de 1 10 377 64 -92us[ -95us] +/- 61ms ^- ntp1.hetzner.de 2 7 377 100 -242us[ -245us] +/- 35ms ^- ntp2.hetzner.de 2 7 377 80 -59us[ -63us] +/- 17ms ^- ntp3.hetzner.de 2 9 377 446 +84us[ +80us] +/- 30ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 20 Jun 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 96 -818us[ -818us] +/- 8628us ^+ 2A10-3781-08Cc.connected> 2 10 377 828 -786us[ -639us] +/- 9002us ^- ntp-public-2.oma.be 2 9 377 29 -2573us[-2573us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 199 -679us[ -679us] +/- 9056us ^+ d54c70bd3.static.telenet> 1 10 377 283 +3342us[+3342us] +/- 9585us ^* 82-64-45-50.subs.proxad.> 1 10 377 507 -330us[ -178us] +/- 8072us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 20 Jun 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 459 -221us[ -221us] +/- 15ms ^+ 2A10-3781-08cC.connected> 2 10 377 447 -1740us[-1740us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 434 -1563us[-1563us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 461 -164us[ -149us] +/- 7861us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 20 Jun 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 465 -110us[ -89us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 10 377 884 +105us[ +120us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 877 -225us[ -210us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 376 -40us[ -17us] +/- 7940us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 20 Jun 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 808 -1001us[-1086us] +/- 12ms ^? 2a10-3781-08cc.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 2 10 377 916 -2746us[-2828us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 922 -1062us[-1145us] +/- 7933us ^+ d54c70bd3.static.telenet> 1 10 377 816 +1837us[+1751us] +/- 9917us ^* 82-64-45-50.subs.proxad.> 1 10 367 776 -1473us[-1559us] +/- 7163us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 20 Jun 17:04:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 923 -177us[ -140us] +/- 8002us ^- time.fu-berlin.de 1 10 377 307 -305us[ -305us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 54 -393us[ -393us] +/- 35ms ^- ntp2.hetzner.de 2 7 377 96 -240us[ -240us] +/- 17ms ^- ntp3.hetzner.de 2 8 377 208 -80us[ -80us] +/- 33ms