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 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 317 +830us[+1006us] +/- 6748us ^* 2a10-3781-08Cc.connected> 2 10 377 17 +636us[ +821us] +/- 7035us ^- ntp-public-2.oma.be 2 10 377 1004 +335us[ +489us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 457 -3271us[-3099us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 456 +7341us[+7513us] +/- 12ms ^+ 82-64-171-216.subs.proxa> 1 10 377 930 +1054us[+1211us] +/- 8765us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 740 -132us[ -44us] +/- 7159us ^- time.fu-berlin.de 1 10 377 411 -788us[ -788us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 455 -193us[ -193us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 95 -612us[ -612us] +/- 25ms ^- ntp3.hetzner.de 2 10 377 102 -507us[ -507us] +/- 22ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 190 -61us[ -39us] +/- 8051us ^- time.fu-berlin.de 1 9 377 369 -172us[ -152us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 229 -90us[ -68us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 859 -202us[ -187us] +/- 38ms ^- ntp3.hetzner.de 2 9 377 248 -110us[ -88us] +/- 19ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 777 +59us[ +88us] +/- 3473us ^* time1.esa.int 1 9 377 448 -200us[ -162us] +/- 3443us ^+ ntp1.time.nl 1 10 377 1026 -374us[ -217us] +/- 4558us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 810 -671us[ -741us] +/- 7364us ^- time.fu-berlin.de 1 10 377 790 -2467us[-2467us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 20m -589us[ -657us] +/- 17ms ^- ntp2.hetzner.de 2 10 377 998 -2842us[-2910us] +/- 40ms ^- ntp3.hetzner.de 2 9 377 350 -761us[ -761us] +/- 19ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 383 -1820us[-1820us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 665 -5936ns[ -23us] +/- 7296us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 19 Jul 21:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 120 -47us[ -37us] +/- 7708us ^- time.fu-berlin.de 1 10 377 1006 -444us[ -434us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 466 -307us[ -297us] +/- 30ms ^- ntp2.hetzner.de 2 9 377 158 -451us[ -441us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 971 -336us[ -326us] +/- 25ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 19 Jul 21:07:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 670 -1875us[-1703us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 77 +65us[ +178us] +/- 6877us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 19 Jul 21:07:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 556 -348us[ -348us] +/- 12ms ^+ 2A10-3781-08CC.connected> 2 10 377 1034 -684us[ +98us] +/- 12ms ^- ntp-public-2.oma.be 2 9 377 505 -3323us[-3323us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 182 -381us[ -381us] +/- 6933us ^+ d54c70bd3.static.telenet> 1 10 377 992 +6359us[+7149us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 824 -254us[ +566us] +/- 5790us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 19 Jul 21:07:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 231 +1959us[+2075us] +/- 13ms ^+ 2a10-3781-08cC.connected> 2 10 377 695 +351us[ +602us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 884 -1295us[-1046us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 132 +653us[ +768us] +/- 8072us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 19 Jul 21:07:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 353 +893us[+1053us] +/- 12ms ^+ 2A10-3781-08cc.connected> 2 10 377 530 -1088us[ -988us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 691 +2410us[+2493us] +/- 40ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 140 +1155us[+1353us] +/- 8047us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 19 Jul 21:07:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 979 -39us[ +205us] +/- 16ms ^- 2a10-3781-08CC.connected> 2 10 377 29 +130us[ +130us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 135 +297us[ +297us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 379 +203us[ +203us] +/- 8016us ^- d54c70bd3.static.telenet> 1 10 377 862 +7532us[+7809us] +/- 14ms ^* 82-64-171-216.subs.proxa> 1 10 377 823 +825us[+1113us] +/- 3988us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 19 Jul 21:07:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 200 -1161us[-1161us] +/- 8702us ^- time.fu-berlin.de 1 10 377 1021 -851us[ -852us] +/- 71ms ^- ntp1.hetzner.de 2 9 377 5 -742us[ -742us] +/- 20ms ^- ntp2.hetzner.de 2 10 377 823 -868us[ -870us] +/- 39ms ^- ntp3.hetzner.de 2 10 377 221 -851us[ -851us] +/- 19ms