DNS response history for ns2.webhoroskop.org

ns2.webhoroskop.org 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 36 DNS check records, 36 successful responses, 0 failed responses, and 447 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.webhoroskop.org.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

447 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.95.201.160

Most recently resolved hosting IP on selected date

Successful Responses

36

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.webhoroskop.org

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
36 2026-08-25 12:39 639232576780683689
355 ms 23.95.201.160
35 2026-08-25 12:21 639232566381512620
339 ms 23.95.201.160
34 2026-08-25 12:04 639232556111768563
176 ms 23.95.201.160
33 2026-08-25 11:47 639232545839529039
461 ms 23.95.201.160
32 2026-08-25 11:30 639232535349285207
176 ms 23.95.201.160
31 2026-08-25 11:12 639232524938080723
335 ms 23.95.201.160
30 2026-08-25 10:19 639232492740373468
340 ms 23.95.201.160
29 2026-08-25 10:01 639232482235303141
338 ms 23.95.201.160
28 2026-08-25 09:44 639232471861770303
182 ms 23.95.201.160
27 2026-08-25 09:27 639232461630217327
168 ms 23.95.201.160
26 2026-08-25 09:10 639232451282965990
450 ms 23.95.201.160
25 2026-08-25 08:52 639232440814614938
167 ms 23.95.201.160
24 2026-08-25 08:35 639232430410720425
338 ms 23.95.201.160
23 2026-08-25 08:18 639232420003096185
169 ms 23.95.201.160
22 2026-08-25 08:00 639232409467287444
163 ms 23.95.201.160
21 2026-08-25 07:43 639232399077195997
354 ms 23.95.201.160
20 2026-08-25 07:25 639232388731528337
338 ms 23.95.201.160
19 2026-08-25 07:08 639232378288598612
461 ms 23.95.201.160
18 2026-08-25 06:14 639232346196373643
4169 ms 23.95.201.160
17 2026-08-25 05:57 639232336112370741
3 ms 23.95.201.160
16 2026-08-25 05:41 639232326146508970
339 ms 23.95.201.160
15 2026-08-25 05:24 639232316189381720
363 ms 23.95.201.160
14 2026-08-25 05:08 639232306217998913
184 ms 23.95.201.160
13 2026-08-25 04:51 639232296255744174
334 ms 23.95.201.160
12 2026-08-25 04:34 639232286095760789
165 ms 23.95.201.160
11 2026-08-25 04:17 639232276086186273
338 ms 23.95.201.160
10 2026-08-25 04:01 639232265900986425
339 ms 23.95.201.160
9 2026-08-25 03:44 639232255723518075
332 ms 23.95.201.160
8 2026-08-25 03:27 639232245484452890
346 ms 23.95.201.160
7 2026-08-25 03:09 639232235157175331
350 ms 23.95.201.160
6 2026-08-25 02:16 639232203197189095
165 ms 23.95.201.160
5 2026-08-25 01:59 639232192844564298
337 ms 23.95.201.160
4 2026-08-25 01:42 639232182496008942
2167 ms 23.95.201.160
3 2026-08-25 01:24 639232172197053132
335 ms 23.95.201.160
2 2026-08-25 00:31 639232140250307418
190 ms 23.95.201.160
1 2026-08-25 00:14 639232129927860324
337 ms 23.95.201.160