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 12 Aug 16:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 371 619 -54us[ -342us] +/- 6250us ^+ 2a10-3781-08cc.connected> 2 10 343 558 -33us[ -324us] +/- 6238us ^- ntp-public-2.oma.be 2 9 377 293 +261us[ -43us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 327 -3651us[-3953us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 165 +4406us[+4097us] +/- 9579us ^+ 82-64-171-216.subs.proxa> 1 10 377 582 +1707us[+1417us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 12 Aug 16:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 28m -153us[ -122us] +/- 7341us ^- time.fu-berlin.de 1 10 377 856 -254us[ -254us] +/- 57ms ^- ntp1.hetzner.de 2 9 377 675 -224us[ -224us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 575 -472us[ -472us] +/- 35ms ^- ntp3.hetzner.de 2 10 377 91 -1826us[-1826us] +/- 18ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 12 Aug 16:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 8 375 194 +135us[ +271us] +/- 7951us ^- time.fu-berlin.de 1 7 377 40 +138us[ +138us] +/- 59ms ^- ntp1.hetzner.de 2 7 377 77 +90us[ +90us] +/- 26ms ^- ntp2.hetzner.de 2 7 377 29 -285us[ -285us] +/- 42ms ^- ntp3.hetzner.de 2 7 377 53 +240us[ +240us] +/- 16ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 12 Aug 16:34:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ time1.esa.int 1 6 377 49 -85us[ -112us] +/- 3811us ^+ ntp1.time.nl 1 6 377 49 -297us[ -325us] +/- 4764us ^* ntp0.nl.uu.net 1 6 377 26 +39us[ +10us] +/- 3310us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 539 -1853us[-1757us] +/- 9135us ^- time.fu-berlin.de 1 10 377 216 -301us[ -301us] +/- 59ms ^+ ntp1.hetzner.de 2 9 377 352 -311us[ -311us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 464 -627us[ -627us] +/- 37ms ^- ntp3.hetzner.de 2 10 377 207 -56us[ -56us] +/- 15ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 312 -1900us[-1897us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 232 -23us[ -20us] +/- 7308us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 355 26 +69us[ +78us] +/- 7952us ^- time.fu-berlin.de 1 10 377 116 +77us[ +86us] +/- 58ms ^- ntp1.hetzner.de 2 8 377 235 +48us[ +57us] +/- 29ms ^- ntp2.hetzner.de 2 7 377 44 -308us[ -299us] +/- 42ms ^- ntp3.hetzner.de 2 8 377 165 +264us[ +273us] +/- 14ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 15 -2645us[-2645us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 949 +7708ns[ +95us] +/- 7055us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 371 978 -480us[ -480us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 343 552 -491us[ -491us] +/- 11ms ^- ntp-public-2.oma.be 2 9 377 14 -3063us[-3063us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 464 -467us[ -467us] +/- 6950us ^+ d54c70bd3.static.telenet> 1 10 377 328 +3704us[+3704us] +/- 10ms ^* 82-64-171-216.subs.proxa> 1 10 377 998 -13us[ -109us] +/- 6133us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 373 478 -2431us[-2431us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 373 483 +230us[ +230us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 309 -1173us[-1173us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 494 -265us[ -270us] +/- 7823us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 371 663 -1677us[-1693us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 371 856 +225us[ +233us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 611 -234us[ -251us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 226 +469us[ +453us] +/- 8071us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 373 467 -2227us[-2117us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 371 984 -2040us[-1962us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 1022 -1652us[-1576us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 1022 +121us[ +197us] +/- 7835us ^- d54c70bd3.static.telenet> 1 10 377 482 +7693us[+7802us] +/- 14ms ^* 82-64-171-216.subs.proxa> 1 10 377 414 +414us[ +526us] +/- 3790us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 12 Aug 16:34:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 983 -418us[ -396us] +/- 8201us ^- time.fu-berlin.de 1 10 377 913 -519us[ -519us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 93 -510us[ -510us] +/- 26ms ^- ntp2.hetzner.de 2 6 377 35 -940us[ -940us] +/- 42ms ^- ntp3.hetzner.de 2 9 377 269 -381us[ -381us] +/- 13ms