DNS response history for ns2.horoscop.live

ns2.horoscop.live 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 30 DNS check records, 30 successful responses, 0 failed responses, and 424 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.horoscop.live.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

424 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.254.16.172

Most recently resolved hosting IP on selected date

Successful Responses

30

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.horoscop.live

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
30 2026-08-25 10:13 639232492740373468
49 ms 5.254.16.172
29 2026-08-25 09:55 639232482235303141
159 ms 5.254.16.172
28 2026-08-25 09:38 639232471861770303
24 ms 5.254.16.172
27 2026-08-25 09:21 639232461630217327
2027 ms 5.254.16.172
26 2026-08-25 09:04 639232451282965990
87 ms 5.254.16.172
25 2026-08-25 08:46 639232440814614938
431 ms 5.254.16.172
24 2026-08-25 08:29 639232430410720425
38 ms 5.254.16.172
23 2026-08-25 08:12 639232420003096185
10 ms 5.254.16.172
22 2026-08-25 07:54 639232409467287444
149 ms 5.254.16.172
21 2026-08-25 07:37 639232399077195997
178 ms 5.254.16.172
20 2026-08-25 07:19 639232388731528337
2098 ms 5.254.16.172
19 2026-08-25 07:02 639232378288598612
17 ms 5.254.16.172
18 2026-08-25 06:08 639232346196373643
3 ms 5.254.16.172
17 2026-08-25 05:52 639232336112370741
23 ms 5.254.16.172
16 2026-08-25 05:35 639232326146508970
636 ms 5.254.16.172
15 2026-08-25 05:18 639232316189381720
13 ms 5.254.16.172
14 2026-08-25 05:02 639232306217998913
4159 ms 5.254.16.172
13 2026-08-25 04:45 639232296255744174
36 ms 5.254.16.172
12 2026-08-25 04:28 639232286095760789
40 ms 5.254.16.172
11 2026-08-25 04:12 639232276086186273
31 ms 5.254.16.172
10 2026-08-25 03:55 639232265900986425
2018 ms 5.254.16.172
9 2026-08-25 03:38 639232255723518075
28 ms 5.254.16.172
8 2026-08-25 03:21 639232245484452890
39 ms 5.254.16.172
7 2026-08-25 03:03 639232235157175331
81 ms 5.254.16.172
6 2026-08-25 02:10 639232203197189095
21 ms 5.254.16.172
5 2026-08-25 01:53 639232192844564298
13 ms 5.254.16.172
4 2026-08-25 01:36 639232182496008942
10 ms 5.254.16.172
3 2026-08-25 01:18 639232172197053132
36 ms 5.254.16.172
2 2026-08-25 00:25 639232140250307418
167 ms 5.254.16.172
1 2026-08-25 00:08 639232129927860324
105 ms 5.254.16.172