DNS response history for ns2.takedown.org

ns2.takedown.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 616 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.takedown.org.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

616 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 07:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

13.248.169.48

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

Showing DNS history for 2026-08-24 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-24 07:05 639231518076817246
2302 ms 13.248.169.48
35 2026-08-24 07:05 639231518076817246
2302 ms 76.223.54.146
34 2026-08-24 06:48 639231508078650885
64 ms 76.223.54.146
33 2026-08-24 06:48 639231508078650885
64 ms 13.248.169.48
32 2026-08-24 06:31 639231498210697093
36 ms 13.248.169.48
31 2026-08-24 06:31 639231498210697093
36 ms 76.223.54.146
30 2026-08-24 06:15 639231488109699360
2112 ms 13.248.169.48
29 2026-08-24 06:15 639231488109699360
2112 ms 76.223.54.146
28 2026-08-24 05:22 639231456772510692
96 ms 76.223.54.146
27 2026-08-24 05:22 639231456772510692
96 ms 13.248.169.48
26 2026-08-24 05:06 639231447084631185
12 ms 76.223.54.146
25 2026-08-24 05:06 639231447084631185
12 ms 13.248.169.48
24 2026-08-24 04:50 639231437208519473
21 ms 76.223.54.146
23 2026-08-24 04:50 639231437208519473
21 ms 13.248.169.48
22 2026-08-24 04:33 639231427209627490
32 ms 76.223.54.146
21 2026-08-24 04:33 639231427209627490
32 ms 13.248.169.48
20 2026-08-24 03:41 639231395791246644
33 ms 76.223.54.146
19 2026-08-24 03:41 639231395791246644
33 ms 13.248.169.48
18 2026-08-24 03:25 639231386075551458
31 ms 76.223.54.146
17 2026-08-24 03:25 639231386075551458
31 ms 13.248.169.48
16 2026-08-24 03:08 639231376208713791
2069 ms 13.248.169.48
15 2026-08-24 03:08 639231376208713791
2069 ms 76.223.54.146
14 2026-08-24 02:51 639231366170589276
12 ms 13.248.169.48
13 2026-08-24 02:51 639231366170589276
12 ms 76.223.54.146
12 2026-08-24 01:59 639231334732159368
22 ms 76.223.54.146
11 2026-08-24 01:59 639231334732159368
22 ms 13.248.169.48
10 2026-08-24 01:43 639231325035670078
4148 ms 76.223.54.146
9 2026-08-24 01:43 639231325035670078
4148 ms 13.248.169.48
8 2026-08-24 01:26 639231315132253837
27 ms 13.248.169.48
7 2026-08-24 01:26 639231315132253837
27 ms 76.223.54.146
6 2026-08-24 01:10 639231305014280808
34 ms 76.223.54.146
5 2026-08-24 01:10 639231305014280808
34 ms 13.248.169.48
4 2026-08-24 00:17 639231273779380675
21 ms 13.248.169.48
3 2026-08-24 00:17 639231273779380675
21 ms 76.223.54.146
2 2026-08-24 00:01 639231264180839154
17 ms 76.223.54.146
1 2026-08-24 00:01 639231264180839154
17 ms 13.248.169.48