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 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 556 +323us[ +323us] +/- 7908us ^+ 2a10-3781-08cc.connected> 2 10 377 548 -325us[ -325us] +/- 7687us ^- ntp-public-2.oma.be 2 7 377 97 +723us[ +723us] +/- 19ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 453 -3780us[-3780us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 615 +3733us[+3595us] +/- 9474us ^+ 82-64-171-216.subs.proxa> 1 10 377 504 +2268us[+2268us] +/- 9700us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 146 -409us[ -493us] +/- 7276us ^- time.fu-berlin.de 1 10 377 562 -451us[ -531us] +/- 61ms ^+ ntp1.hetzner.de 2 10 377 980 -574us[ -648us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 449 -1367us[-1448us] +/- 38ms ^- ntp3.hetzner.de 2 10 377 189 -704us[ -789us] +/- 44ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 365 -942us[ -905us] +/- 8093us ^- time.fu-berlin.de 1 10 377 299 -1006us[-1006us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 398 -1194us[-1157us] +/- 26ms ^- ntp2.hetzner.de 2 8 377 83 -2067us[-2067us] +/- 43ms ^- ntp3.hetzner.de 2 10 377 1100 -1211us[-1176us] +/- 29ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 126 +341us[ +944us] +/- 3611us ^+ time1.esa.int 1 10 377 219 +331us[ +926us] +/- 4013us ^+ ntp1.time.nl 1 10 377 789 -75us[ +471us] +/- 5446us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 494 -43us[ -91us] +/- 7093us ^- time.fu-berlin.de 1 10 377 898 -796us[ -841us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 28m -400us[ -439us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 526 -1335us[-1383us] +/- 37ms ^- ntp3.hetzner.de 2 10 377 938 -2331us[-2377us] +/- 35ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 7 377 5 -948us[ -948us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 279 +567us[ +585us] +/- 9277us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 177 495 -213us[ -176us] +/- 8082us ^- time.fu-berlin.de 1 10 377 169 -443us[ -443us] +/- 67ms ^- ntp1.hetzner.de 2 9 377 403 -639us[ -639us] +/- 25ms ^- ntp2.hetzner.de 2 7 377 11 -1572us[-1572us] +/- 44ms ^- ntp3.hetzner.de 2 8 377 169 -746us[ -746us] +/- 43ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 8 377 62 -1124us[-1124us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 690 -545us[ -681us] +/- 7919us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 159 -155us[ -155us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 271 +260us[ +260us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 290 -819us[ -819us] +/- 46ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 174 +1639us[+1639us] +/- 8041us ^+ d54c70bd3.static.telenet> 1 10 377 285 +5385us[+5385us] +/- 9506us ^* 82-64-171-216.subs.proxa> 1 10 377 306 +767us[+1037us] +/- 5887us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 770 +191us[ +493us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 662 -1325us[-1012us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 717 -580us[ -273us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 287 +1655us[+2005us] +/- 8168us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 2 Aug 20:16:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 859 +263us[ +181us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 880 -2155us[-2242us] +/- 14ms ^+ ntp-public-2.oma.be 2 10 377 875 -855us[ -941us] +/- 43ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 126 +1024us[+1021us] +/- 7945us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 2 Aug 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 361 -1633us[-1356us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 345 -582us[ -306us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 799 -533us[ -228us] +/- 42ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 117 -161us[ -161us] +/- 8094us ^+ d54c70bd3.static.telenet> 1 10 377 871 +5113us[+5423us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 339 -152us[ +124us] +/- 3986us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 2 Aug 20:16:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 712 +455us[ +497us] +/- 8147us ^- time.fu-berlin.de 1 10 377 22 +428us[ +428us] +/- 70ms ^- ntp1.hetzner.de 2 7 377 50 +157us[ +157us] +/- 31ms ^- ntp2.hetzner.de 2 8 377 222 -672us[ -672us] +/- 40ms ^- ntp3.hetzner.de 2 8 377 97 +73us[ +73us] +/- 44ms