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)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* erquy.linocomm.net 2 10 377 82 +555us[+1076us] +/- 6225us ^+ 2A10-3781-08cc.connected> 2 10 377 475 +527us[+1019us] +/- 6247us ^- ntp-public-2.oma.be 2 8 377 242 +692us[+1201us] +/- 44ms ^+ ntp0.rrze.uni-erlangen.de 1 7 377 116 -3176us[-2658us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 195 +5257us[+5769us] +/- 11ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 581 +1080us[+1564us] +/- 9883us
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 283 -375us[ -386us] +/- 7586us ^- time.fu-berlin.de 1 10 377 110 -181us[ -181us] +/- 64ms ^- ntp1.hetzner.de 2 10 377 121 -807us[ -807us] +/- 29ms ^+ ntp2.hetzner.de 2 10 377 312 -2299us[-2310us] +/- 29ms ^- ntp3.hetzner.de 2 9 377 86 -251us[ -251us] +/- 31ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 56 -1457us[-1455us] +/- 9915us ^- time.fu-berlin.de 1 9 377 430 -745us[ -743us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 320 -1964us[-1962us] +/- 29ms ^- ntp2.hetzner.de 2 9 377 462 -259us[ -258us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 357 +715ns[+2664ns] +/- 26ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 676 -30us[ -45us] +/- 3715us ^* time1.esa.int 1 9 377 158 +46us[ +31us] +/- 3500us ^+ ntp1.time.nl 1 9 377 122 +93us[ +93us] +/- 4178us
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 307 -228us[ -480us] +/- 7248us ^- time.fu-berlin.de 1 10 377 705 -344us[ -597us] +/- 59ms ^- ntp1.hetzner.de 2 10 377 400 -742us[ -995us] +/- 26ms ^+ ntp2.hetzner.de 2 10 377 419 -377us[ -629us] +/- 26ms ^- ntp3.hetzner.de 2 10 377 728 -311us[ -564us] +/- 37ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 10 377 942 -2159us[-2169us] +/- 35ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 879 -38us[ -48us] +/- 7179us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 783 -193us[ -143us] +/- 7904us ^- time.fu-berlin.de 1 10 377 187 -176us[ -176us] +/- 63ms ^- ntp1.hetzner.de 2 9 377 54 -625us[ -625us] +/- 31ms ^+ ntp2.hetzner.de 2 9 377 22 -333us[ -333us] +/- 29ms ^- ntp3.hetzner.de 2 10 377 248 -197us[ -197us] +/- 27ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 2 9 377 192 -3011us[-3011us] +/- 46ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 513 +292ns[ -11us] +/- 7008us
Current performance for ntp21.linocomm.net (Roubaix, FR)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 805 -288us[ -260us] +/- 12ms ^+ 2A10-3781-08CC.connected> 2 10 377 678 -572us[ -544us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 102 -3402us[-3402us] +/- 48ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 677 -582us[ -554us] +/- 7034us ^+ d54c70bd3.static.telenet> 1 10 377 18 +2495us[+2495us] +/- 8878us ^+ 82-64-45-50.subs.proxad.> 1 10 377 900 -372us[ -345us] +/- 7239us
Current performance for ntp22.linocomm.net (Paris, FR)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 725 -161us[ -368us] +/- 12ms ^+ 2a10-3781-08cC.connected> 2 10 377 123 -1752us[-1752us] +/- 13ms ^- ntp-public-2.oma.be 2 10 377 411 -2142us[-2339us] +/- 47ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 225 +48us[ -144us] +/- 8229us
Current performance for ntp23.linocomm.net (Paris, FR)
Sun 12 Jul 01:40:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 385 -213us[ -189us] +/- 11ms ^+ 2A10-3781-08cC.connected> 2 10 377 1018 +203us[ +317us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 398 -336us[ -313us] +/- 49ms ^* ntp0.rrze.uni-erlangen.de 1 8 377 249 +74us[ +98us] +/- 7915us
Current performance for ntp24.linocomm.net (Paris, FR)
Sun 12 Jul 01:40:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 350 -2399us[-2332us] +/- 12ms ^+ 2a10-3781-08CC.connected> 2 10 377 512 -390us[ -326us] +/- 11ms ^- ntp-public-2.oma.be 2 10 377 666 -2216us[-2153us] +/- 43ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 38 -631us[ -631us] +/- 7924us ^+ d54c70bd3.static.telenet> 1 10 377 29m +3244us[+3460us] +/- 9261us ^* 82-64-45-50.subs.proxad.> 1 9 377 219 -74us[-5565ns] +/- 5486us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Sun 12 Jul 01:40:02 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 620 -384us[ -424us] +/- 8315us ^- time.fu-berlin.de 1 10 377 333 -129us[ -129us] +/- 61ms ^- ntp1.hetzner.de 2 10 377 871 -616us[ -656us] +/- 51ms ^- ntp2.hetzner.de 2 9 377 213 -290us[ -290us] +/- 27ms ^- ntp3.hetzner.de 2 10 377 214 -175us[ -175us] +/- 28ms