DNS response history for ns2.holditdown.net

ns2.holditdown.net 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 39 DNS check records, 39 successful responses, 0 failed responses, and 414 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.holditdown.net.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.10.117.59

Most recently resolved hosting IP on selected date

Successful Responses

39

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.holditdown.net

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
39 2026-08-25 13:17 639232597643611557
159 ms 52.10.117.59
38 2026-08-25 12:59 639232587225721862
337 ms 52.10.117.59
37 2026-08-25 12:42 639232576780683689
330 ms 52.10.117.59
36 2026-08-25 12:25 639232566381512620
175 ms 52.10.117.59
35 2026-08-25 12:07 639232556111768563
329 ms 52.10.117.59
34 2026-08-25 11:50 639232545839529039
312 ms 52.10.117.59
33 2026-08-25 11:33 639232535349285207
340 ms 52.10.117.59
32 2026-08-25 11:15 639232524938080723
162 ms 52.10.117.59
31 2026-08-25 10:22 639232492740373468
164 ms 52.10.117.59
30 2026-08-25 10:05 639232482235303141
164 ms 52.10.117.59
29 2026-08-25 09:47 639232471861770303
170 ms 52.10.117.59
28 2026-08-25 09:30 639232461630217327
327 ms 52.10.117.59
27 2026-08-25 09:13 639232451282965990
4 ms 52.10.117.59
26 2026-08-25 08:55 639232440814614938
329 ms 52.10.117.59
25 2026-08-25 08:38 639232430410720425
334 ms 52.10.117.59
24 2026-08-25 08:21 639232420003096185
1429 ms 52.10.117.59
23 2026-08-25 08:03 639232409467287444
162 ms 52.10.117.59
22 2026-08-25 07:46 639232399077195997
170 ms 52.10.117.59
21 2026-08-25 07:28 639232388731528337
333 ms 52.10.117.59
20 2026-08-25 07:11 639232378288598612
181 ms 52.10.117.59
19 2026-08-25 06:17 639232346196373643
7 ms 52.10.117.59
18 2026-08-25 06:00 639232336112370741
160 ms 52.10.117.59
17 2026-08-25 05:44 639232326146508970
4164 ms 52.10.117.59
16 2026-08-25 05:27 639232316189381720
169 ms 52.10.117.59
15 2026-08-25 05:11 639232306217998913
328 ms 52.10.117.59
14 2026-08-25 04:54 639232296255744174
4 ms 52.10.117.59
13 2026-08-25 04:37 639232286095760789
339 ms 52.10.117.59
12 2026-08-25 04:20 639232276086186273
338 ms 52.10.117.59
11 2026-08-25 04:04 639232265900986425
162 ms 52.10.117.59
10 2026-08-25 03:47 639232255723518075
321 ms 52.10.117.59
9 2026-08-25 03:30 639232245484452890
160 ms 52.10.117.59
8 2026-08-25 03:12 639232235157175331
2160 ms 52.10.117.59
7 2026-08-25 02:19 639232203197189095
322 ms 52.10.117.59
6 2026-08-25 02:02 639232192844564298
330 ms 52.10.117.59
5 2026-08-25 01:45 639232182496008942
313 ms 52.10.117.59
4 2026-08-25 01:27 639232172197053132
319 ms 52.10.117.59
3 2026-08-25 00:34 639232140250307418
316 ms 52.10.117.59
2 2026-08-25 00:17 639232129927860324
161 ms 52.10.117.59
1 2026-08-25 00:00 639232119551972438
162 ms 52.10.117.59