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 10 Jul 21:10:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 904 +405us[ +323us] +/- 6607us ^+ 2A10-3781-08CC.connected> 2 10 377 671 +335us[ +335us] +/- 6829us ^- ntp-public-2.oma.be 2 9 377 360 +942us[ +942us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 184 -2691us[-2691us] +/- 10ms ^+ d54c70bd3.static.telenet> 1 10 377 7 +6393us[+6393us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 505 +1731us[+1731us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 29 -155us[ -80us] +/- 7592us ^- time.fu-berlin.de 1 10 377 907 -605us[ -539us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 510 -303us[ -233us] +/- 25ms ^+ ntp2.hetzner.de 2 10 377 92 -136us[ -61us] +/- 14ms ^- ntp3.hetzner.de 2 10 377 962 -199us[ -133us] +/- 17ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 367 930 +8108ns[ +57us] +/- 8299us ^- time.fu-berlin.de 1 10 377 21m -625us[ -579us] +/- 74ms ^- ntp1.hetzner.de 2 10 377 378 +33us[ +33us] +/- 25ms ^+ ntp2.hetzner.de 2 9 377 219 -1344us[-1344us] +/- 13ms ^- ntp3.hetzner.de 2 10 377 175 +146us[ +146us] +/- 10ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 514 +730us[ +836us] +/- 4329us ^* time1.esa.int 1 9 377 423 +393us[ +503us] +/- 3558us ^+ ntp1.time.nl 1 10 377 1028 +217us[ +447us] +/- 5254us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 337 158 -273us[ -273us] +/- 7529us ^- time.fu-berlin.de 1 10 377 515 -371us[ -374us] +/- 68ms ^- ntp1.hetzner.de 2 10 377 695 -371us[ -375us] +/- 23ms ^+ ntp2.hetzner.de 2 10 377 228 -335us[ -335us] +/- 11ms ^- ntp3.hetzner.de 2 9 377 11 -333us[ -333us] +/- 14ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 851 -2067us[-2067us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 905 -2688ns[+5073ns] +/- 7139us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 593 -9272ns[ -43us] +/- 7870us ^- time.fu-berlin.de 1 10 377 989 -108us[ -153us] +/- 62ms ^- ntp1.hetzner.de 2 7 377 115 -172us[ -172us] +/- 29ms ^+ ntp2.hetzner.de 2 7 377 51 -58us[ -58us] +/- 14ms ^- ntp3.hetzner.de 2 8 377 121 -42us[ -42us] +/- 11ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 330 -2947us[-3011us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 271 -30us[ -97us] +/- 7038us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 630 -633us[ -442us] +/- 11ms ^+ 2a10-3781-08Cc.connected> 2 9 377 387 -351us[ -351us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 884 -2898us[-2726us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 445 -21us[ +184us] +/- 6841us ^+ d54c70bd3.static.telenet> 1 10 377 793 +3324us[+3503us] +/- 8963us ^+ 82-64-45-50.subs.proxad.> 1 10 377 691 +99us[ +285us] +/- 7439us
Current performance for ntp22.linocomm.net (Paris, FR)
Fri 10 Jul 21:10:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 588 +188us[ +188us] +/- 12ms ^+ 2A10-3781-08CC.connected> 2 10 377 783 +116us[ +116us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 158 +1915us[+1915us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 973 +733us[+1064us] +/- 8086us
Current performance for ntp23.linocomm.net (Paris, FR)
Fri 10 Jul 21:10:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 231 +425us[ +425us] +/- 14ms ^+ 2A10-3781-08cc.connected> 2 10 377 785 +323us[ +459us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 201 -1147us[-1147us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 510 +905us[+1043us] +/- 8076us
Current performance for ntp24.linocomm.net (Paris, FR)
Fri 10 Jul 21:10:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 180 -339us[ -339us] +/- 11ms ^+ 2A10-3781-08Cc.connected> 2 10 377 763 -105us[+9745ns] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 400 +394us[ +534us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 684 +407us[ +528us] +/- 7818us ^+ d54c70bd3.static.telenet> 1 10 377 559 +4578us[+4707us] +/- 9744us ^* 82-64-45-50.subs.proxad.> 1 10 377 205 +926us[+1080us] +/- 5660us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Fri 10 Jul 21:10:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 469 +151us[ +215us] +/- 7546us ^- time.fu-berlin.de 1 9 377 179 -247us[ -247us] +/- 59ms ^- ntp1.hetzner.de 2 9 377 439 -210us[ -210us] +/- 24ms ^+ ntp2.hetzner.de 2 7 377 111 -123us[ -123us] +/- 13ms ^- ntp3.hetzner.de 2 7 377 110 -142us[ -142us] +/- 11ms