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 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 625 +919us[ +919us] +/- 7651us ^+ 2A10-3781-08cc.connected> 2 10 377 534 +409us[ +409us] +/- 6616us ^- ntp-public-2.oma.be 2 10 377 438 +547us[ +547us] +/- 38ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 241 -3479us[-3479us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 864 +4063us[+4405us] +/- 9622us ^+ 82-64-45-50.subs.proxad.> 1 10 377 378 +2723us[+2723us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 791 -1989us[-2014us] +/- 9244us ^- time.fu-berlin.de 1 10 377 538 -238us[ -238us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 706 -139us[ -139us] +/- 20ms ^- ntp2.hetzner.de 2 9 377 72 +1187us[+1187us] +/- 37ms ^- ntp3.hetzner.de 2 9 377 465 -508us[ -508us] +/- 35ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 836 -1410us[-1382us] +/- 9335us ^- time.fu-berlin.de 1 9 377 294 -342us[ -342us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 234 -1094us[-1094us] +/- 26ms ^- ntp2.hetzner.de 2 8 377 199 +931us[ +931us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 273 -624us[ -624us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 113 -256us[ -256us] +/- 3841us ^* time1.esa.int 1 10 377 570 -211us[ -479us] +/- 3742us ^+ ntp1.time.nl 1 9 377 372 -67us[ -67us] +/- 4290us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 330 -587us[ -796us] +/- 8472us ^- time.fu-berlin.de 1 10 377 553 -271us[ -476us] +/- 59ms ^+ ntp1.hetzner.de 2 10 377 466 -812us[-1019us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 568 +1355us[+1150us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 339 -196us[ -405us] +/- 37ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 643 -1714us[-1863us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 193 -60us[ -210us] +/- 7205us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 343 -108us[ -40us] +/- 7872us ^- time.fu-berlin.de 1 10 377 726 -326us[ -262us] +/- 73ms ^- ntp1.hetzner.de 2 8 377 177 -121us[ -121us] +/- 26ms ^- ntp2.hetzner.de 2 9 377 58 +946us[ +946us] +/- 36ms ^- ntp3.hetzner.de 2 9 377 423 -569us[ -502us] +/- 34ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 8 Jul 17:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 196 -1750us[-1750us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 425 +11us[ +20us] +/- 6990us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 8 Jul 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 167 +206us[ +235us] +/- 12ms ^+ 2A10-3781-08cc.connected> 2 10 377 799 +257us[ +285us] +/- 12ms ^- ntp-public-2.oma.be 2 8 377 216 -2799us[-2770us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 36 -14us[ +16us] +/- 7198us ^+ d54c70bd3.static.telenet> 1 10 377 606 +6010us[+6038us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 537 +639us[ +667us] +/- 7752us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 8 Jul 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 503 -158us[ -190us] +/- 12ms ^+ 2a10-3781-08cC.connected> 2 10 377 641 -2133us[-2173us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 1028 +48us[+3987ns] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 83 +39us[+6874ns] +/- 8251us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 8 Jul 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 98 +4895ns[+4895ns] +/- 15ms ^+ 2A10-3781-08Cc.connected> 2 10 377 24m +88us[+2487ns] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 988 -31us[ -112us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 952 +211us[ +130us] +/- 8162us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 8 Jul 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 931 -46us[ +38us] +/- 12ms ^+ 2A10-3781-08cc.connected> 2 10 377 138 -2024us[-2024us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 255 -2314us[-2314us] +/- 30ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 957 -323us[ -239us] +/- 7858us ^+ d54c70bd3.static.telenet> 1 10 377 387 +3693us[+3693us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 10 377 443 +410us[ +498us] +/- 5922us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 8 Jul 17:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 210 -175us[ -149us] +/- 8087us ^- time.fu-berlin.de 1 10 377 458 -262us[ -237us] +/- 61ms ^- ntp1.hetzner.de 2 8 377 45 -81us[ -81us] +/- 28ms ^- ntp2.hetzner.de 2 9 377 413 +1029us[+1054us] +/- 31ms ^- ntp3.hetzner.de 2 9 377 266 -555us[ -529us] +/- 37ms