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)
Sat 18 Jul 05:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 258 -75us[ -75us] +/- 6219us ^* 2a10-3781-08CC.connected> 2 10 377 496 -336us[ -626us] +/- 7249us ^- ntp-public-2.oma.be 2 9 377 75 +60us[ +60us] +/- 37ms ^+ ntp0.rrze.uni-erlangen.de 1 8 377 211 -3983us[-3983us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 949 +4077us[+3877us] +/- 9573us ^+ 82-64-171-216.subs.proxa> 1 10 377 812 -869us[-1096us] +/- 10ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sat 18 Jul 05:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 578 -488us[ -504us] +/- 7670us ^- time.fu-berlin.de 1 10 377 380 -489us[ -489us] +/- 58ms ^- ntp1.hetzner.de 2 9 377 105 -376us[ -376us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 497 -183us[ -183us] +/- 32ms ^- ntp3.hetzner.de 2 10 377 547 -224us[ -224us] +/- 31ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sat 18 Jul 05:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 277 147 -229us[ -206us] +/- 7996us ^- time.fu-berlin.de 1 10 377 297 -404us[ -382us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 158 -349us[ -327us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 744 -206us[ -184us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 633 -220us[ -198us] +/- 28ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sat 18 Jul 05:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 36 -123us[ -123us] +/- 3860us ^* time1.esa.int 1 10 377 312 +30us[ +244us] +/- 3405us ^+ ntp1.time.nl 1 10 377 403 -42us[ +163us] +/- 4341us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sat 18 Jul 05:43:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 704 -162us[ -162us] +/- 7439us ^- time.fu-berlin.de 1 10 377 655 -2282us[-2282us] +/- 71ms ^- ntp1.hetzner.de 2 10 377 110 -204us[ -204us] +/- 18ms ^- ntp2.hetzner.de 2 10 377 21m -192us[ -192us] +/- 33ms ^- ntp3.hetzner.de 2 10 377 178 -216us[ -216us] +/- 36ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 202 -2112us[-2112us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 404 -42us[ -47us] +/- 7147us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 9 -1445us[-1468us] +/- 8828us ^- time.fu-berlin.de 1 10 377 391 -1020us[-1043us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 326 -924us[ -947us] +/- 15ms ^- ntp2.hetzner.de 2 10 377 36 -873us[ -896us] +/- 25ms ^- ntp3.hetzner.de 2 9 377 30 -915us[ -938us] +/- 37ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 533 -2901us[-2901us] +/- 32ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 683 -57us[ -70us] +/- 7013us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 908 -1362us[-1454us] +/- 11ms ^- 2A10-3781-08Cc.connected> 2 10 377 330 -1395us[-1395us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 868 -3989us[-4081us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 104 -1111us[-1111us] +/- 7023us ^+ d54c70bd3.static.telenet> 1 10 377 863 +3099us[+3007us] +/- 9319us ^* 82-64-171-216.subs.proxa> 1 10 377 712 -470us[ -563us] +/- 6054us
Current performance for ntp22.linocomm.net (Paris, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 132 +1701us[+1701us] +/- 13ms ^+ 2A10-3781-08CC.connected> 2 10 377 665 -2004us[-1955us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 671 +252us[ +302us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 143 +315us[ +350us] +/- 7872us
Current performance for ntp23.linocomm.net (Paris, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 9 377 108 +452us[ +452us] +/- 15ms ^+ 2a10-3781-08cC.connected> 2 10 377 387 +353us[ +565us] +/- 12ms ^- ntp-public-2.oma.be 2 10 377 370 +428us[ +641us] +/- 37ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 246 +787us[+1004us] +/- 8108us
Current performance for ntp24.linocomm.net (Paris, FR)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- erquy.linocomm.net 2 10 377 782 -2260us[-2217us] +/- 14ms ^- 2A10-3781-08CC.connected> 2 10 377 967 -2606us[-2565us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 854 -570us[ -527us] +/- 46ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 221 -135us[ -135us] +/- 8160us ^+ d54c70bd3.static.telenet> 1 10 377 778 +5607us[+5649us] +/- 13ms ^* 82-64-171-216.subs.proxa> 1 10 377 623 -139us[ -96us] +/- 3562us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sat 18 Jul 05:43:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 11 -226us[ -205us] +/- 7951us ^- time.fu-berlin.de 1 10 377 907 -383us[ -364us] +/- 66ms ^- ntp1.hetzner.de 2 9 377 504 -287us[ -267us] +/- 22ms ^- ntp2.hetzner.de 2 10 377 833 -239us[ -219us] +/- 25ms ^- ntp3.hetzner.de 2 8 377 21 -302us[ -282us] +/- 37ms