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)
Fri 4 Sep 12:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 445 -369us[ -286us] +/- 6280us ^+ 2a10-3781-08cc.connected> 2 10 377 619 -22us[ +58us] +/- 6299us ^- ntp-public-2.oma.be 2 9 377 178 +125us[ +125us] +/- 39ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 22m -150us[ -78us] +/- 6694us ^* d54c70bd3.static.telenet> 1 10 377 429 +2278us[+2361us] +/- 7695us ^+ 82-64-171-216.subs.proxa> 1 10 377 518 +1633us[+1714us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 4 Sep 12:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 375 931 -129us[ -412us] +/- 7267us ^- time.fu-berlin.de 1 10 377 328 -88us[ -88us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 759 +266us[ +266us] +/- 36ms ^- ntp2.hetzner.de 2 9 377 871 -247us[ -247us] +/- 37ms ^- ntp3.hetzner.de 2 9 377 41 +125us[ +125us] +/- 30ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 4 Sep 12:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 1 -276us[ -283us] +/- 8064us ^- time.fu-berlin.de 1 10 377 138 -358us[ -366us] +/- 63ms ^- ntp1.hetzner.de 2 10 377 197 +65us[ +58us] +/- 32ms ^- ntp2.hetzner.de 2 7 377 41 -318us[ -326us] +/- 16ms ^- ntp3.hetzner.de 2 8 377 140 -190us[ -198us] +/- 27ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 4 Sep 12:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 668 -173us[ -127us] +/- 3426us ^+ time1.esa.int 1 10 377 31m -99us[ -29us] +/- 3280us ^+ ntp1.time.nl 1 10 377 36 -32us[ -32us] +/- 4338us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 79 -629us[ -613us] +/- 8046us ^- time.fu-berlin.de 1 10 377 661 -558us[ -542us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 181 +61us[ +77us] +/- 31ms ^- ntp2.hetzner.de 2 9 377 425 -538us[ -523us] +/- 23ms ^- ntp3.hetzner.de 2 10 377 453 -354us[ -338us] +/- 24ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 720 -1406us[-1394us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 33 +751ns[ +13us] +/- 7158us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 279 -188us[ -275us] +/- 7998us ^- time.fu-berlin.de 1 10 377 965 -232us[ -309us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 351 +206us[ +120us] +/- 43ms ^- ntp2.hetzner.de 2 7 377 70 -220us[ -220us] +/- 16ms ^+ ntp3.hetzner.de 2 7 377 93 -50us[ -50us] +/- 28ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 35 -1461us[-1461us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 431 -13us[ -19us] +/- 6919us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 118 -119us[ -119us] +/- 9254us ^+ 2a10-3781-08cc.connected> 2 10 377 868 -262us[ -291us] +/- 9451us ^- ntp-public-2.oma.be 2 9 377 296 -1595us[-1595us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 418 -124us[ -124us] +/- 6928us ^+ d54c70bd3.static.telenet> 1 10 377 31m +5015us[+4775us] +/- 11ms ^* 82-64-171-216.subs.proxa> 1 10 377 615 +8283ns[ -29us] +/- 5251us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 812 -3576us[-3620us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 197 -2610us[-2610us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 187 -1838us[-1838us] +/- 45ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 519 -289us[ -333us] +/- 8184us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 604 -2709us[-2880us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 249 -600us[ -710us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 343 -1683us[-1789us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 90 -265us[ -383us] +/- 8091us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 685 -893us[ -975us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 776 -4321us[-4401us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 790 -1912us[-1993us] +/- 42ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 916 -703us[ -781us] +/- 7996us ^+ d54c70bd3.static.telenet> 1 10 377 537 +1130us[+1045us] +/- 7111us ^* 82-64-171-216.subs.proxa> 1 10 377 171 -212us[ -303us] +/- 3903us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 4 Sep 12:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 273 331 -229us[ -249us] +/- 7908us ^- time.fu-berlin.de 1 9 377 143 -242us[ -242us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 19 +267us[ +267us] +/- 34ms ^- ntp2.hetzner.de 2 6 377 42 -207us[ -207us] +/- 16ms ^- ntp3.hetzner.de 2 7 377 84 +4004ns[+4004ns] +/- 28ms