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)
Sat 29 Aug 04:46:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 613 -309us[ -16us] +/- 6973us ^+ 2a10-3781-08cc.connected> 2 10 377 701 -407us[ -116us] +/- 6739us ^- ntp-public-2.oma.be 2 8 377 130 -259us[ +71us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 20 +32us[ +364us] +/- 6825us ^+ d54c70bd3.static.telenet> 1 10 377 53 +8730us[+9061us] +/- 14ms ^+ 82-64-171-216.subs.proxa> 1 10 377 505 +1073us[+1396us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 954 -115us[ -49us] +/- 7435us ^- time.fu-berlin.de 1 10 377 1 -355us[ -355us] +/- 66ms ^+ ntp1.hetzner.de 2 10 377 1028 -76us[ -11us] +/- 13ms ^- ntp2.hetzner.de 2 9 377 484 -181us[ -181us] +/- 31ms ^+ ntp3.hetzner.de 2 10 377 21m -71us[ -10us] +/- 22ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 370 -1554us[-1629us] +/- 8514us ^- time.fu-berlin.de 1 9 377 177 -1087us[-1087us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 287 -901us[ -901us] +/- 19ms ^- ntp2.hetzner.de 2 7 377 222 -1034us[-1034us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 982 -927us[ -999us] +/- 16ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 1016 -72us[ -73us] +/- 3496us ^+ time1.esa.int 1 10 377 939 +271us[ +271us] +/- 3340us ^+ ntp1.time.nl 1 10 377 360 +322us[ +322us] +/- 4275us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 32m -284us[ -293us] +/- 7521us ^- time.fu-berlin.de 1 10 377 471 -442us[ -442us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 333 -283us[ -283us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 110 -308us[ -308us] +/- 37ms ^- ntp3.hetzner.de 2 10 377 31m -491us[ -491us] +/- 26ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 326 -1848us[-1848us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 602 -29us[ -35us] +/- 7264us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 17 -253us[ -246us] +/- 8154us ^- time.fu-berlin.de 1 10 377 158 -434us[ -427us] +/- 64ms ^+ ntp1.hetzner.de 2 10 377 642 -302us[ -295us] +/- 17ms ^- ntp2.hetzner.de 2 9 377 179 -417us[ -410us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 560 -379us[ -372us] +/- 23ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 206 -1811us[-1831us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 203 -6417ns[ -26us] +/- 6942us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 567 -640us[ -640us] +/- 9171us ^+ 2a10-3781-08cc.connected> 2 9 377 298 -688us[ -688us] +/- 9451us ^- ntp-public-2.oma.be 2 10 377 443 -2133us[-2133us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 746 -223us[ -223us] +/- 6994us ^+ d54c70bd3.static.telenet> 1 10 377 628 +3019us[+3019us] +/- 7860us ^* 82-64-171-216.subs.proxa> 1 10 377 813 -39us[ -35us] +/- 5329us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 980 -122us[ -169us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 92 -2464us[-2511us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 400 -2371us[-2424us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 18 +10us[ -38us] +/- 7986us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 210 -1823us[-1796us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 231 -2162us[-2134us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 148 -1722us[-1695us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 135 -320us[ -293us] +/- 7903us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 502 -2599us[-2591us] +/- 13ms ^- 2a10-3781-08cc.connected> 2 10 377 602 -398us[ -389us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 484 -416us[ -407us] +/- 29ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 448 -218us[ -210us] +/- 7809us ^- d54c70bd3.static.telenet> 1 10 377 280 +5358us[+5365us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 43 +174us[ +180us] +/- 3959us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 29 Aug 04:46:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 996 -693us[ -266us] +/- 8487us ^- time.fu-berlin.de 1 10 377 106 -401us[ -401us] +/- 65ms ^- ntp1.hetzner.de 2 9 377 117 -235us[ -235us] +/- 22ms ^- ntp2.hetzner.de 2 9 377 379 -435us[ -435us] +/- 31ms ^- ntp3.hetzner.de 2 7 377 101 -350us[ -350us] +/- 16ms