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 Apr 18:52:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 435 -1370us[-1661us] +/- 8607us ^+ 2a10-3781-08cc.connected> 2 10 377 519 -924us[-1222us] +/- 7952us ^- ntp-public-2.oma.be 2 9 377 364 +912us[ +626us] +/- 21ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 363 -4586us[-4871us] +/- 11ms ^* d54c70bd3.static.telenet> 1 10 377 307 +4773us[+4492us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 166 -376us[ -376us] +/- 10ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Wed 8 Apr 18:52:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntp0.nl.uu.net 1 10 377 989 +996us[+1070us] +/- 4087us ^+ time1.esa.int 1 10 377 378 +496us[ +496us] +/- 3847us ^+ ntp1.time.nl 1 10 377 794 -524us[ -524us] +/- 4676us
Current performance for ntp5.linocomm.net (Paris, FR)
Wed 8 Apr 18:52:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 643 -2394us[-2394us] +/- 14ms ^+ 2a10-3781-08cc.connected> 2 10 377 1 -474us[ -474us] +/- 13ms ^* ntp0.nl.uu.net 1 10 377 721 +350us[ +394us] +/- 5516us ^+ time1.esa.int 1 10 377 456 -1485us[-1485us] +/- 7604us ^+ ntp1.time.nl 1 10 377 927 -68us[ -27us] +/- 7311us
Current performance for ntp9.linocomm.net (Nürnberg, DE)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 816 -456us[ -322us] +/- 7803us ^- time.fu-berlin.de 1 10 377 627 -575us[ -575us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 808 -629us[ -629us] +/- 49ms ^- ntp2.hetzner.de 2 10 377 26m -750us[ -620us] +/- 45ms ^- ntp3.hetzner.de 2 9 377 244 -451us[ -451us] +/- 36ms
Current performance for ntp16.linocomm.net (Gravelines, DE)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 34m -294us[ -329us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 408 -54us[ -91us] +/- 7209us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 357 18 -1271us[-1279us] +/- 9351us ^- time.fu-berlin.de 1 10 377 612 -298us[ -305us] +/- 62ms ^- ntp1.hetzner.de 2 9 377 197 -151us[ -159us] +/- 30ms ^+ ntp2.hetzner.de 2 10 377 970 -201us[ -208us] +/- 30ms ^- ntp3.hetzner.de 2 9 377 461 -178us[ -186us] +/- 31ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 668 -481us[ -476us] +/- 34ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 173 +34us[ +40us] +/- 7006us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 20 -143us[ -150us] +/- 8095us ^- time.fu-berlin.de 1 10 377 958 -379us[ -385us] +/- 72ms ^+ ntp1.hetzner.de 2 10 377 245 -235us[ -241us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 716 -250us[ -256us] +/- 34ms ^- ntp3.hetzner.de 2 10 377 891 -188us[ -194us] +/- 25ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 111 -1141us[-1141us] +/- 11ms ^+ 2a10-3781-08cc.connected> 2 10 377 882 -806us[ -699us] +/- 10ms ^- ntp-public-2.oma.be 2 10 377 168 -352us[ -352us] +/- 25ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 300 -77us[ +33us] +/- 6900us ^+ d54c70bd3.static.telenet> 1 10 377 522 +3366us[+3475us] +/- 8239us ^+ 82-64-45-50.subs.proxad.> 1 10 377 652 +278us[ +386us] +/- 7479us
Current performance for ntp22.linocomm.net (Paris, FR)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 664 +1322us[+1485us] +/- 12ms ^+ 2a10-3781-08cc.connected> 2 10 377 976 +1072us[+1259us] +/- 11ms ^+ ntp-public-2.oma.be 2 10 377 137 +4813us[+4813us] +/- 31ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 583 -4069us[-3912us] +/- 14ms
Current performance for ntp23.linocomm.net (Paris, FR)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 628 +2995us[+3065us] +/- 14ms ^* 2a10-3781-08cc.connected> 2 10 377 628 -669us[ -599us] +/- 14ms ^- ntp-public-2.oma.be 2 10 377 510 +4868us[+4868us] +/- 41ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 772 -3522us[-3454us] +/- 14ms
Current performance for ntp24.linocomm.net (Paris, FR)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 785 -277us[ -340us] +/- 12ms ^- 2a10-3781-08cc.connected> 2 10 377 331 -2514us[-2514us] +/- 15ms ^- ntp-public-2.oma.be 2 10 377 1004 +1280us[+1218us] +/- 32ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 162 -5426us[-5426us] +/- 14ms ^+ d54c70bd3.static.telenet> 1 10 377 71 +3100us[+3100us] +/- 11ms ^* 82-64-45-50.subs.proxad.> 1 10 377 591 +601us[ +538us] +/- 5326us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Wed 8 Apr 18:52:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 871 -391us[ -399us] +/- 8346us ^- time.fu-berlin.de 1 10 377 944 -436us[ -443us] +/- 72ms ^- ntp1.hetzner.de 2 10 377 280 -279us[ -279us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 722 -368us[ -368us] +/- 34ms ^- ntp3.hetzner.de 2 9 377 326 -274us[ -274us] +/- 33ms