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 19 Aug 10:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 272 +137us[ +137us] +/- 6747us ^* 2a10-3781-08cc.connected> 2 10 377 432 -9952ns[ -53us] +/- 6632us ^- ntp-public-2.oma.be 2 9 377 236 +136us[ +136us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 365 -3938us[-3938us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 51 +1747us[+1747us] +/- 6310us ^+ 82-64-171-216.subs.proxa> 1 10 377 430 +646us[ +646us] +/- 8365us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 112 -318us[ -369us] +/- 7909us ^- time.fu-berlin.de 1 10 377 39 -2651us[-2651us] +/- 66ms ^- ntp1.hetzner.de 2 10 377 3 -102us[ -102us] +/- 15ms ^- ntp2.hetzner.de 2 10 377 552 +1202us[+1160us] +/- 40ms ^- ntp3.hetzner.de 2 10 377 420 +799us[ +754us] +/- 30ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 30m -313us[ -326us] +/- 8103us ^- time.fu-berlin.de 1 10 377 201 -365us[ -365us] +/- 62ms ^- ntp1.hetzner.de 2 10 377 462 -266us[ -266us] +/- 13ms ^- ntp2.hetzner.de 2 9 377 325 +1089us[+1089us] +/- 19ms ^- ntp3.hetzner.de 2 9 377 317 +258us[ +258us] +/- 29ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 809 -34us[ -86us] +/- 3376us ^* time1.esa.int 1 10 377 56 -1992ns[ -63us] +/- 3231us ^+ ntp1.time.nl 1 10 377 525 -40us[ -96us] +/- 4312us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 706 -2256us[-2257us] +/- 9366us ^- time.fu-berlin.de 1 10 377 269 -567us[ -567us] +/- 60ms ^+ ntp1.hetzner.de 2 10 377 483 -368us[ -368us] +/- 12ms ^- ntp2.hetzner.de 2 10 377 404 +959us[ +959us] +/- 42ms ^- ntp3.hetzner.de 2 10 377 392 +80us[ +80us] +/- 30ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 971 -1636us[-1613us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 462 +49us[ +73us] +/- 7211us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 8 373 336 -1679us[-1677us] +/- 7934us ^- time.fu-berlin.de 1 10 377 1008 -1853us[-1907us] +/- 65ms ^- ntp1.hetzner.de 2 10 377 810 -1679us[-1677us] +/- 15ms ^- ntp2.hetzner.de 2 7 377 22 -348us[ -348us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 775 -1198us[-1196us] +/- 22ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 140 -1691us[-1691us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 576 -4428ns[ -22us] +/- 6852us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 376 -28us[ -28us] +/- 9233us ^+ 2a10-3781-08cc.connected> 2 9 377 346 -149us[ -149us] +/- 9135us ^- ntp-public-2.oma.be 2 10 377 944 -1699us[-1949us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 311 -52us[ -52us] +/- 7052us ^+ d54c70bd3.static.telenet> 1 10 377 824 +4711us[+4711us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 935 +208us[ -43us] +/- 5644us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 101 -49us[ -49us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 751 -2009us[-2591us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 697 -120us[ -188us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 195 -256us[ -370us] +/- 7817us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 172 -880us[ -880us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 78 -3421us[-3421us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 644 -804us[-1013us] +/- 29ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 255 -1048us[-1278us] +/- 7806us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 201 -824us[ -824us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 867 -2232us[-2299us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 219 -2304us[-2304us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 226 -438us[ -438us] +/- 7800us ^+ d54c70bd3.static.telenet> 1 10 377 399 +6274us[+6274us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 410 -482us[ -559us] +/- 4010us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 19 Aug 10:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 63 -310us[ -783us] +/- 7887us ^- time.fu-berlin.de 1 9 377 59 -500us[ -500us] +/- 64ms ^- ntp1.hetzner.de 2 9 377 428 -296us[ -767us] +/- 14ms ^- ntp2.hetzner.de 2 9 377 249 +1029us[ +558us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 271 +219us[ -253us] +/- 30ms