DNS response history for ns2.horlogo.com

ns2.horlogo.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 540 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.horlogo.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

540 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.69.195.37

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.horlogo.com

Showing DNS history for 2026-08-25 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
33 2026-08-25 11:48 639232545839529039
119 ms 158.69.195.37
32 2026-08-25 11:31 639232535349285207
444 ms 158.69.195.37
31 2026-08-25 11:13 639232524938080723
433 ms 158.69.195.37
30 2026-08-25 10:20 639232492740373468
9 ms 158.69.195.37
29 2026-08-25 10:02 639232482235303141
405 ms 158.69.195.37
28 2026-08-25 09:45 639232471861770303
434 ms 158.69.195.37
27 2026-08-25 09:28 639232461630217327
426 ms 158.69.195.37
26 2026-08-25 09:11 639232451282965990
423 ms 158.69.195.37
25 2026-08-25 08:53 639232440814614938
444 ms 158.69.195.37
24 2026-08-25 08:36 639232430410720425
434 ms 158.69.195.37
23 2026-08-25 08:19 639232420003096185
446 ms 158.69.195.37
22 2026-08-25 08:01 639232409467287444
2104 ms 158.69.195.37
21 2026-08-25 07:44 639232399077195997
432 ms 158.69.195.37
20 2026-08-25 07:26 639232388731528337
431 ms 158.69.195.37
19 2026-08-25 07:09 639232378288598612
440 ms 158.69.195.37
18 2026-08-25 06:15 639232346196373643
423 ms 158.69.195.37
17 2026-08-25 05:58 639232336112370741
2139 ms 158.69.195.37
16 2026-08-25 05:42 639232326146508970
429 ms 158.69.195.37
15 2026-08-25 05:25 639232316189381720
10 ms 158.69.195.37
14 2026-08-25 05:09 639232306217998913
2448 ms 158.69.195.37
13 2026-08-25 04:52 639232296255744174
451 ms 158.69.195.37
12 2026-08-25 04:35 639232286095760789
436 ms 158.69.195.37
11 2026-08-25 04:18 639232276086186273
8 ms 158.69.195.37
10 2026-08-25 04:02 639232265900986425
447 ms 158.69.195.37
9 2026-08-25 03:45 639232255723518075
453 ms 158.69.195.37
8 2026-08-25 03:28 639232245484452890
447 ms 158.69.195.37
7 2026-08-25 03:10 639232235157175331
427 ms 158.69.195.37
6 2026-08-25 02:17 639232203197189095
432 ms 158.69.195.37
5 2026-08-25 02:00 639232192844564298
430 ms 158.69.195.37
4 2026-08-25 01:43 639232182496008942
120 ms 158.69.195.37
3 2026-08-25 01:25 639232172197053132
433 ms 158.69.195.37
2 2026-08-25 00:32 639232140250307418
438 ms 158.69.195.37
1 2026-08-25 00:15 639232129927860324
434 ms 158.69.195.37