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)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 708 -342us[ -885us] +/- 7249us ^+ 2a10-3781-08cc.connected> 2 10 377 116 -538us[ -538us] +/- 6456us ^- ntp-public-2.oma.be 2 8 377 208 -289us[ -289us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 203 -3866us[-3866us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 541 +3972us[+3972us] +/- 9408us ^+ 82-64-171-216.subs.proxa> 1 10 377 859 +667us[ +134us] +/- 8403us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 997 -330us[ -338us] +/- 7310us ^- time.fu-berlin.de 1 9 377 621 -412us[ -412us] +/- 71ms ^- ntp1.hetzner.de 2 8 377 70 -357us[ -357us] +/- 35ms ^- ntp2.hetzner.de 2 8 377 52 -219us[ -219us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 386 -403us[ -403us] +/- 29ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 719 -859us[ -711us] +/- 8995us ^- time.fu-berlin.de 1 9 377 126 -461us[ -461us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 450 -50us[ -50us] +/- 31ms ^- ntp2.hetzner.de 2 7 377 30 -30us[ -30us] +/- 19ms ^+ ntp3.hetzner.de 2 10 377 337 -228us[ -228us] +/- 29ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* time1.esa.int 1 10 377 689 +77us[ +348us] +/- 3216us ^+ ntp1.time.nl 1 10 377 28m -213us[ +21us] +/- 4523us ^+ ntp0.nl.uu.net 1 10 377 287 +145us[ +145us] +/- 3310us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 240 -322us[ -252us] +/- 7546us ^- time.fu-berlin.de 1 10 377 1109 -449us[ -385us] +/- 64ms ^+ ntp1.hetzner.de 2 9 377 456 -446us[ -378us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 752 -2232us[-2166us] +/- 18ms ^- ntp3.hetzner.de 2 9 377 333 -528us[ -459us] +/- 30ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 384 -1329us[-1329us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 828 +385us[ +432us] +/- 9054us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 424 -142us[ -102us] +/- 8035us ^- time.fu-berlin.de 1 10 377 197 -355us[ -355us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 213 -233us[ -233us] +/- 34ms ^- ntp2.hetzner.de 2 8 377 62 -189us[ -189us] +/- 19ms ^- ntp3.hetzner.de 2 9 377 255 -404us[ -404us] +/- 30ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 751 -2151us[-2180us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 489 -68us[ -98us] +/- 6952us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 879 -1098us[-1118us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 793 -1212us[-1231us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 557 -3789us[-3807us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 709 +223us[ +205us] +/- 7991us ^+ d54c70bd3.static.telenet> 1 10 377 312 +5922us[+5906us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 287 -444us[ -459us] +/- 6023us
Current performance for ntp22.linocomm.net (Paris, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 630 -488us[ -318us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 251 +366us[ +519us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 85 -1941us[-1786us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 5 +213us[ +369us] +/- 7905us
Current performance for ntp23.linocomm.net (Paris, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 562 -2002us[-2004us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 450 -70us[ -70us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 1003 -1823us[-1808us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 51 +415us[ +425us] +/- 8135us
Current performance for ntp24.linocomm.net (Paris, FR)
Mon 17 Aug 01:31:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 714 -476us[ -406us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 286 -1753us[-1753us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 775 -388us[ -318us] +/- 40ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 457 +35us[ +106us] +/- 7887us ^- d54c70bd3.static.telenet> 1 10 377 828 +6468us[+6538us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 312 +311us[ +382us] +/- 3586us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Mon 17 Aug 01:31:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 356 -114us[ -116us] +/- 7832us ^- time.fu-berlin.de 1 9 377 394 -23us[ -26us] +/- 60ms ^- ntp1.hetzner.de 2 8 377 128 +59us[ +59us] +/- 35ms ^- ntp2.hetzner.de 2 7 377 37 +53us[ +53us] +/- 19ms ^- ntp3.hetzner.de 2 10 377 720 -115us[ -118us] +/- 23ms