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 5 Aug 10:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 973 -827us[-2374us] +/- 6189us ^+ 2a10-3781-08cc.connected> 2 10 377 477 -1074us[-1074us] +/- 6540us ^- ntp-public-2.oma.be 2 8 377 220 -1310us[-1310us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 320 -4950us[-4950us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 893 +1769us[+1769us] +/- 9073us ^+ 82-64-171-216.subs.proxa> 1 10 377 724 +1083us[+1083us] +/- 9861us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 5 Aug 10:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 405 -2312us[-2388us] +/- 11ms ^- time.fu-berlin.de 1 10 377 844 -707us[ -780us] +/- 62ms ^- ntp1.hetzner.de 2 8 377 71 -434us[ -434us] +/- 19ms ^- ntp2.hetzner.de 2 9 377 25m -1575us[-1651us] +/- 41ms ^- ntp3.hetzner.de 2 10 377 540 -37us[ -112us] +/- 36ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 5 Aug 10:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 718 -631us[ -622us] +/- 10ms ^- time.fu-berlin.de 1 10 377 527 -985us[ -985us] +/- 68ms ^+ ntp1.hetzner.de 2 8 377 14 -141us[ -141us] +/- 21ms ^+ ntp2.hetzner.de 2 8 377 132 +611us[ +611us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 336 +334us[ +334us] +/- 37ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 5 Aug 10:25:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 1037 -32us[ -161us] +/- 3376us ^+ time1.esa.int 1 10 377 766 -250us[ -250us] +/- 3546us ^+ ntp1.time.nl 1 10 377 520 +59us[ +59us] +/- 4354us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 796 -884us[ -867us] +/- 9276us ^- time.fu-berlin.de 1 10 377 1143 -721us[ -706us] +/- 73ms ^+ ntp1.hetzner.de 2 9 377 55 -645us[ -645us] +/- 19ms ^- ntp2.hetzner.de 2 9 377 243 +177us[ +177us] +/- 28ms ^- ntp3.hetzner.de 2 8 377 89 -157us[ -157us] +/- 42ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 10 377 615 -1604us[-1912us] +/- 22ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 305 +770us[ +424us] +/- 9334us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 85 -338us[ -328us] +/- 9766us ^- time.fu-berlin.de 1 10 377 472 -260us[ -251us] +/- 68ms ^- ntp1.hetzner.de 2 8 377 188 -163us[ -153us] +/- 18ms ^- ntp2.hetzner.de 2 8 377 165 +611us[ +621us] +/- 27ms ^- ntp3.hetzner.de 2 8 377 77 +335us[ +335us] +/- 41ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 220 -2739us[-2739us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 525 -714us[ -740us] +/- 7969us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 580 -738us[ -590us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 742 -902us[ -754us] +/- 11ms ^- ntp-public-2.oma.be 2 8 377 11 -3714us[-3714us] +/- 31ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 843 -1613us[-1464us] +/- 8000us ^+ d54c70bd3.static.telenet> 1 10 377 588 +3040us[+3188us] +/- 8177us ^* 82-64-171-216.subs.proxa> 1 10 377 504 -228us[ -81us] +/- 6045us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 189 -841us[ -836us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 68 -969us[ -969us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 1012 -926us[ -924us] +/- 50ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 79 -814us[ -810us] +/- 7893us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 185 -2338us[-2338us] +/- 13ms ^+ 2a10-3781-08cc.connected> 2 10 377 693 +186us[ +143us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 909 -2135us[-2156us] +/- 53ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 226 -200us[ -181us] +/- 8048us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 5 Aug 10:25:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 646 -1070us[-1549us] +/- 11ms ^- 2a10-3781-08cc.connected> 2 10 377 839 -470us[ -917us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 180 -2296us[-2755us] +/- 33ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 114 -264us[ -264us] +/- 8094us ^+ d54c70bd3.static.telenet> 1 10 377 155 +1750us[+1289us] +/- 9220us ^* 82-64-171-216.subs.proxa> 1 9 377 124 -236us[ -699us] +/- 3834us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 5 Aug 10:25:03 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 974 -462us[ -669us] +/- 9850us ^- time.fu-berlin.de 1 10 377 398 -588us[ -588us] +/- 69ms ^- ntp1.hetzner.de 2 7 377 1 -442us[ -442us] +/- 21ms ^- ntp2.hetzner.de 2 6 377 22 +263us[ +263us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 351 +25us[ +25us] +/- 37ms