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)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 362 +105us[ -489us] +/- 6128us ^* 2a10-3781-08cc.connected> 2 9 377 354 +341us[ -256us] +/- 6049us ^- ntp-public-2.oma.be 2 7 377 82 +282us[ +282us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 93 -3899us[-3899us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 586 +6274us[+5735us] +/- 11ms ^- 82-64-171-216.subs.proxa> 1 10 377 928 -633us[-1178us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 23m -571us[ -611us] +/- 7425us ^- time.fu-berlin.de 1 10 377 309 -551us[ -551us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 66 -89us[ -89us] +/- 30ms ^- ntp2.hetzner.de 2 10 377 252 -103us[ -103us] +/- 45ms ^- ntp3.hetzner.de 2 9 377 385 -123us[ -123us] +/- 42ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 613 -588us[ -617us] +/- 8464us ^- time.fu-berlin.de 1 10 377 34m -278us[ -471us] +/- 73ms ^- ntp1.hetzner.de 2 9 377 1102 -98us[ -114us] +/- 35ms ^- ntp2.hetzner.de 2 10 377 448 +73us[ +73us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 317 +41us[ +41us] +/- 42ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 9 377 38 -359us[ -359us] +/- 3817us ^* time1.esa.int 1 9 377 411 -185us[ -152us] +/- 3641us ^+ ntp1.time.nl 1 9 377 75 -366us[ -366us] +/- 4784us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 314 -587us[ -714us] +/- 7440us ^- time.fu-berlin.de 1 10 377 559 -731us[ -859us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 901 -2418us[-2545us] +/- 34ms ^- ntp2.hetzner.de 2 10 377 517 -400us[ -527us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 956 -502us[ -629us] +/- 33ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 7 377 76 -1591us[-1591us] +/- 27ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 462 -42us[ -81us] +/- 7138us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 320 -572us[ -570us] +/- 8108us ^- time.fu-berlin.de 1 10 377 792 -532us[ -530us] +/- 61ms ^- ntp1.hetzner.de 2 9 377 230 -272us[ -272us] +/- 28ms ^- ntp2.hetzner.de 2 7 377 68 -217us[ -217us] +/- 23ms ^- ntp3.hetzner.de 2 8 377 179 -328us[ -328us] +/- 43ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 721 -1007us[ -975us] +/- 33ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 20 +450us[ +468us] +/- 6988us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 129 -697us[ -697us] +/- 8779us ^+ 2a10-3781-08cc.connected> 2 10 377 373 -661us[ -661us] +/- 8516us ^+ ntp-public-2.oma.be 2 9 377 117 -2104us[-2104us] +/- 27ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 233 -515us[ -515us] +/- 6943us ^+ d54c70bd3.static.telenet> 1 10 377 357 +6402us[+6402us] +/- 12ms ^* 82-64-171-216.subs.proxa> 1 10 377 818 -34us[ -64us] +/- 6064us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 505 -221us[ -231us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 880 +238us[ +388us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 765 +164us[ +313us] +/- 36ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 184 +125us[ +114us] +/- 7824us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 30 Jul 05:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 995 +1380us[+1395us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 62 -1900us[-1900us] +/- 12ms ^+ ntp-public-2.oma.be 2 10 377 1011 +403us[ +418us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 93 +433us[ +429us] +/- 8124us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 30 Jul 05:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 894 +882us[+1011us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 933 -343us[ -217us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 914 +121us[ +248us] +/- 34ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 50 +91us[ +91us] +/- 8181us ^- d54c70bd3.static.telenet> 1 10 377 1019 +6659us[+6778us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 9 377 61 +223us[ +353us] +/- 3757us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 30 Jul 05:49:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 560 -618us[ -601us] +/- 8127us ^- time.fu-berlin.de 1 10 377 40 -640us[ -640us] +/- 72ms ^- ntp1.hetzner.de 2 7 377 122 -257us[ -257us] +/- 30ms ^- ntp2.hetzner.de 2 7 377 60 -275us[ -275us] +/- 23ms ^- ntp3.hetzner.de 2 8 377 60 -325us[ -325us] +/- 20ms