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)
Wed 1 Jul 00:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 305 +232us[ +232us] +/- 7338us ^* 2A10-3781-08cC.connected> 2 10 377 811 +193us[ +159us] +/- 7256us ^- ntp-public-2.oma.be 2 10 377 521 +643us[ +643us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 807 -2891us[-2891us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 215 +6905us[+6905us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 972 +1159us[+1125us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 1 Jul 00:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 7 -572us[ -636us] +/- 7639us ^- time.fu-berlin.de 1 10 377 397 -322us[ -385us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 211 -421us[ -485us] +/- 31ms ^- ntp2.hetzner.de 2 10 377 430 -758us[ -821us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 803 -368us[ -430us] +/- 24ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 1 Jul 00:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 506 -1192us[-1051us] +/- 9091us ^- time.fu-berlin.de 1 9 377 6 -1118us[-1118us] +/- 64ms ^+ ntp1.hetzner.de 2 10 377 1000 -385us[ -246us] +/- 22ms ^- ntp2.hetzner.de 2 8 377 207 -887us[ -887us] +/- 43ms ^- ntp3.hetzner.de 2 9 377 160 -670us[ -670us] +/- 31ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 1 Jul 00:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 896 +211us[ +538us] +/- 3414us ^* time1.esa.int 1 10 377 244 +222us[ +576us] +/- 3555us ^+ ntp1.time.nl 1 10 377 975 +82us[ +406us] +/- 4493us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 1 Jul 00:28:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 701 -1925us[-2002us] +/- 8868us ^- time.fu-berlin.de 1 9 377 478 -513us[ -513us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 433 -532us[ -532us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 177 -889us[ -889us] +/- 45ms ^- ntp3.hetzner.de 2 9 377 439 -539us[ -539us] +/- 28ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 490 -2503us[-2587us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 166 -655us[ -740us] +/- 7141us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 898 -754us[ -841us] +/- 7670us ^- time.fu-berlin.de 1 10 377 39 -1054us[-1054us] +/- 63ms ^- ntp1.hetzner.de 2 8 377 259 -1143us[-1143us] +/- 31ms ^- ntp2.hetzner.de 2 8 377 229 -1447us[-1447us] +/- 43ms ^- ntp3.hetzner.de 2 8 377 84 -1260us[-1260us] +/- 32ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 400 -2404us[-2404us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 876 -662us[ -632us] +/- 9094us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 1 Jul 00:28:06 UTC 2026
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 285 -1387us[-1167us] +/- 11ms ^+ 2A10-3781-08CC.connected> 2 10 377 577 -412us[ -271us] +/- 12ms ^+ ntp-public-2.oma.be 2 8 377 60 -1286us[-1286us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 150 +1474us[+1731us] +/- 8032us ^+ d54c70bd3.static.telenet> 1 10 377 944 +7202us[+7683us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 297 +882us[+1098us] +/- 7376us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 1037 +237us[ +250us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 254 -2106us[-2106us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 773 +1911us[+1898us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 459 +782us[ +770us] +/- 8160us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 1 Jul 00:28:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 872 -231us[ -202us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 107 +537us[ +537us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 863 +347us[ +376us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 502 +557us[ +593us] +/- 7972us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 1 Jul 00:28:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 124 -2479us[-2479us] +/- 13ms ^+ 2A10-3781-08cC.connected> 2 10 377 83 -686us[ -686us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 571 -497us[ -539us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 110 -403us[ -403us] +/- 7874us ^+ d54c70bd3.static.telenet> 1 10 377 20m +9332us[+9283us] +/- 16ms ^* 82-64-45-50.subs.proxad.> 1 10 377 388 +99us[ +60us] +/- 5542us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 1 Jul 00:28:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 390 -137us[ -142us] +/- 8057us ^- time.fu-berlin.de 1 9 377 444 -132us[ -136us] +/- 72ms ^+ ntp1.hetzner.de 2 9 377 220 -190us[ -190us] +/- 32ms ^- ntp2.hetzner.de 2 9 377 328 -563us[ -563us] +/- 41ms ^- ntp3.hetzner.de 2 8 377 13 -327us[ -327us] +/- 33ms