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)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 367 +67us[ +67us] +/- 6409us ^* 2a10-3781-08cc.connected> 2 10 375 661 +203us[ +108us] +/- 6193us ^- ntp-public-2.oma.be 3 9 377 421 +177us[ +177us] +/- 26ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 248 -3721us[-3721us] +/- 11ms ^+ d54c70bd3.static.telenet> 1 10 377 45 +3145us[+3145us] +/- 8892us ^+ 82-64-45-50.subs.proxad.> 1 10 377 380 -624us[ -624us] +/- 12ms
Current performance for ntp2.linocomm.net (Nuremberg, DE)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 600 -618us[ -594us] +/- 7256us ^- time.fu-berlin.de 1 10 377 559 -910us[ -910us] +/- 57ms ^- ntp1.hetzner.de 2 10 377 535 -726us[ -726us] +/- 33ms ^- ntp2.hetzner.de 2 10 377 965 -618us[ -595us] +/- 33ms ^- ntp3.hetzner.de 2 10 377 33m -571us[ -551us] +/- 42ms
Current performance for ntp3.linocomm.net (Falkenstein, DE)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 39 -428us[ -779us] +/- 8282us ^- time.fu-berlin.de 1 9 377 109 -270us[ -614us] +/- 61ms ^+ ntp1.hetzner.de 2 10 377 495 -80us[ -387us] +/- 35ms ^- ntp2.hetzner.de 2 8 377 87 -13us[ -360us] +/- 30ms ^- ntp3.hetzner.de 2 10 377 704 -54us[ -340us] +/- 28ms
Current performance for ntp4.linocomm.net (Donkerbroek, NL)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp0.nl.uu.net 1 10 377 19 +468us[ +468us] +/- 3848us ^* time1.esa.int 1 9 377 266 +33us[ +39us] +/- 3557us ^+ ntp1.time.nl 1 10 377 772 -481us[ -477us] +/- 5729us
Current performance for ntp5.linocomm.net (Paris, FR)
Sun 7 Jun 08:34:01 UTC 2026
Current performance for ntp9.linocomm.net (Nuremberg, DE)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 693 -460us[ -474us] +/- 7513us ^- time.fu-berlin.de 1 10 377 406 -841us[ -841us] +/- 60ms ^- ntp1.hetzner.de 2 10 377 838 -336us[ -350us] +/- 29ms ^- ntp2.hetzner.de 2 10 377 24m -311us[ -325us] +/- 31ms ^- ntp3.hetzner.de 2 10 377 152 -381us[ -381us] +/- 38ms
Current performance for ntp16.linocomm.net (Gravelines, FR)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ ntp-public-2.oma.be 3 10 377 726 -1331us[-1464us] +/- 23ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 62 +451us[ +296us] +/- 9310us
Current performance for ntp17.linocomm.net (Falkenstein, DE)
Thu 11 Jun 20:49:01 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 867 -1433us[-1416us] +/- 8452us ^- time.fu-berlin.de 1 10 377 320 -1137us[-1137us] +/- 58ms ^- ntp1.hetzner.de 2 10 377 591 -854us[ -854us] +/- 34ms ^- ntp2.hetzner.de 2 10 377 244 -901us[ -901us] +/- 28ms ^- ntp3.hetzner.de 2 9 377 489 -868us[ -868us] +/- 31ms
Current performance for ntp18.linocomm.net (Roubaix, FR)
Thu 11 Jun 20:49:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^- ntp-public-2.oma.be 3 9 377 369 -2016us[-2016us] +/- 28ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 472 +34us[ +42us] +/- 9110us
Current performance for ntp20.linocomm.net (Falkenstein, DE)
Thu 11 Jun 20:49:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 975 -574us[ -606us] +/- 7902us ^- time.fu-berlin.de 1 10 377 46 -661us[ -661us] +/- 58ms ^+ ntp1.hetzner.de 2 10 377 945 -411us[ -411us] +/- 34ms ^- ntp2.hetzner.de 2 9 377 509 -358us[ -358us] +/- 24ms ^- ntp3.hetzner.de 2 9 377 416 -415us[ -415us] +/- 32ms
Current performance for ntp21.linocomm.net (Roubaix, FR)
Thu 11 Jun 20:49:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 8 377 188 -635us[ -395us] +/- 8696us ^+ 2a10-3781-08cc.connected> 2 10 377 128 -468us[ -228us] +/- 8825us ^- ntp-public-2.oma.be 3 10 377 628 -2335us[-2094us] +/- 24ms ^+ ntp0.rrze.uni-erlangen.de 1 10 377 123 -406us[ -167us] +/- 8936us ^* d54c70bd3.static.telenet> 1 10 377 112 +6552us[+6791us] +/- 12ms ^+ 82-64-45-50.subs.proxad.> 1 10 377 890 -140us[ +102us] +/- 7468us
Current performance for ntp22.linocomm.net (Paris, FR)
Thu 11 Jun 20:49:06 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 491 -443us[ -443us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 10 377 504 -2142us[-2142us] +/- 13ms ^- ntp-public-2.oma.be 3 10 377 72 -2020us[-2020us] +/- 38ms ^* ntp0.rrze.uni-erlangen.de 1 10 377 956 +326us[ +422us] +/- 8065us
Current performance for ntp23.linocomm.net (Paris, FR)
Thu 11 Jun 20:49:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 430 +3860us[+3772us] +/- 15ms ^? 2a10-3781-08cC.connected> 0 10 0 - +0ns[ +0ns] +/- 0ns ^- ntp-public-2.oma.be 3 10 377 766 +384us[ +292us] +/- 26ms ^* ntp0.rrze.uni-erlangen.de 1 9 377 49 +222us[ +136us] +/- 8000us
Current performance for ntp24.linocomm.net (Paris, FR)
Thu 11 Jun 20:49:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^+ erquy.linocomm.net 2 10 377 433 -240us[ -283us] +/- 11ms ^+ 2a10-3781-08cC.connected> 2 10 377 575 -153us[ -197us] +/- 11ms ^- ntp-public-2.oma.be 3 10 377 638 -216us[ -259us] +/- 28ms ^+ ntp0.rrze.uni-erlangen.de 1 9 377 420 +56us[ +13us] +/- 7948us ^+ d54c70bd3.static.telenet> 1 10 377 196 +6240us[+6197us] +/- 13ms ^* 82-64-45-50.subs.proxad.> 1 10 377 108 +917us[ +874us] +/- 5866us
Current performance for ntp25.linocomm.net (Falkenstein, DE)
Thu 11 Jun 20:49:07 UTC 2026 MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^* ntps1-0.eecsit.tu-berlin> 1 10 377 530 -1666us[-1666us] +/- 8459us ^- time.fu-berlin.de 1 10 377 702 -1078us[-1078us] +/- 60ms ^- ntp1.hetzner.de 2 9 377 249 -860us[ -860us] +/- 23ms ^- ntp2.hetzner.de 2 9 377 30 -855us[ -855us] +/- 31ms ^- ntp3.hetzner.de 2 8 377 143 -943us[ -943us] +/- 36ms