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 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 112 +311us[ +311us] +/- 6973us ^* 2a10-3781-08cc.connected> 2 10 377 665 +230us[ +64us] +/- 6468us ^- ntp-public-2.oma.be 2 8 377 202 -551us[ -551us] +/- 14ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 810 -3809us[-3970us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 850 +7032us[+6872us] +/- 13ms ^x 82-64-171-216.subs.proxa> 1 6 377 21 +577ms[ +577ms] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 690 +130us[ +127us] +/- 8480us ^- time.fu-berlin.de 1 10 377 546 -304us[ -304us] +/- 70ms ^- ntp1.hetzner.de 2 10 377 22m +233us[ +230us] +/- 27ms ^- ntp2.hetzner.de 2 10 377 480 +1124ns[+1124ns] +/- 24ms ^- ntp3.hetzner.de 2 10 377 121 -416us[ -416us] +/- 43ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 928 -307us[ -307us] +/- 8027us ^- time.fu-berlin.de 1 10 377 226 -290us[ -290us] +/- 61ms ^+ ntp1.hetzner.de 2 10 377 342 +187us[ +187us] +/- 27ms ^- ntp2.hetzner.de 2 9 377 725 -1152us[-1152us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 567 -521us[ -521us] +/- 35ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 269 +427us[ +427us] +/- 3662us ^* time1.esa.int 1 10 377 671 +214us[ +218us] +/- 3751us ^+ ntp1.time.nl 1 10 377 806 -212us[ -207us] +/- 4432us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 499 -444us[ -565us] +/- 7407us ^- time.fu-berlin.de 1 10 377 795 -398us[ -518us] +/- 67ms ^+ ntp1.hetzner.de 2 10 377 636 +88us[ -32us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 796 -448us[ -567us] +/- 20ms ^- ntp3.hetzner.de 2 10 377 184 -715us[ -715us] +/- 42ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 8 377 184 -2826us[-2822us] +/- 16ms ^* ntp0.rrze.uni-erlangen.de 1 7 377 53 +37us[ +40us] +/- 7195us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 27m -177us[ -136us] +/- 7635us ^- time.fu-berlin.de 1 10 377 38 -673us[ -673us] +/- 63ms ^- ntp1.hetzner.de 2 8 377 159 -151us[ -151us] +/- 30ms ^- ntp2.hetzner.de 2 6 377 49 -503us[ -503us] +/- 29ms ^- ntp3.hetzner.de 2 9 377 37 -791us[ -791us] +/- 42ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 2 9 377 331 -1903us[-2142us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 14 +589us[ +316us] +/- 6985us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 29 Jul 20:07:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 404 +13us[ +635us] +/- 9284us ^+ 2a10-3781-08cc.connected> 2 10 377 613 -362us[ +259us] +/- 8750us ^+ ntp-public-2.oma.be 2 8 377 89 -2708us[-2708us] +/- 17ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 479 -277us[ +344us] +/- 6969us ^+ d54c70bd3.static.telenet> 1 10 377 619 +6931us[+7552us] +/- 12ms ^x 82-64-171-216.subs.proxa> 1 6 377 33 +39ms[ +39ms] +/- 6040us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 29 Jul 20:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 713 +1785us[+1883us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 649 +156us[ +254us] +/- 10ms ^+ ntp-public-2.oma.be 2 10 377 1008 -601us[ -503us] +/- 42ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 416 +338us[ +436us] +/- 7866us
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 29 Jul 20:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 159 +403us[ +403us] +/- 15ms ^+ 2a10-3781-08cc.connected> 2 10 377 309 +158us[ +158us] +/- 11ms ^+ ntp-public-2.oma.be 2 10 377 233 -753us[ -753us] +/- 19ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 574 -12us[ +12us] +/- 7895us
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 29 Jul 20:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 124 +67us[ +67us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 132 -1849us[-1849us] +/- 13ms ^+ ntp-public-2.oma.be 2 10 377 112 -1026us[-1026us] +/- 21ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 210 +285us[ +251us] +/- 8082us ^+ d54c70bd3.static.telenet> 1 10 377 237 +3472us[+3438us] +/- 11ms ^x 82-64-171-216.subs.proxa> 1 6 377 36 +287ms[ +287ms] +/- 3716us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 29 Jul 20:07:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 795 -115us[ -105us] +/- 8081us ^- time.fu-berlin.de 1 10 377 347 -112us[ -112us] +/- 59ms ^- ntp1.hetzner.de 2 8 377 104 +418us[ +418us] +/- 31ms ^- ntp2.hetzner.de 2 6 377 47 +59us[ +59us] +/- 29ms ^- ntp3.hetzner.de 2 8 377 176 -217us[ -217us] +/- 40ms