DNS response history for ns2.nft2bc.com

ns2.nft2bc.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-24. For this date, NameServerHistory found 38 DNS check records, 37 successful responses, 1 failed responses, and 321 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.nft2bc.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

321 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

37

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.nft2bc.com

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
38 2026-08-24 15:52 639231828211839931
4 ms 162.240.160.133
37 2026-08-24 15:36 639231818080917481
353 ms 162.240.160.133
36 2026-08-24 15:18 639231807961539652
346 ms 162.240.160.133
35 2026-08-24 15:02 639231797631669865
342 ms 162.240.160.133
34 2026-08-24 14:08 639231765923559455
355 ms 162.240.160.133
33 2026-08-24 13:52 639231755868832964
345 ms 162.240.160.133
32 2026-08-24 13:35 639231745628278877
354 ms 162.240.160.133
31 2026-08-24 13:18 639231735407682062
353 ms 162.240.160.133
30 2026-08-24 12:25 639231703815441688
348 ms 162.240.160.133
29 2026-08-24 12:08 639231693747052549
184 ms 162.240.160.133
28 2026-08-24 11:51 639231683712487276
351 ms 162.240.160.133
27 2026-08-24 11:35 639231673513573868
9 ms 162.240.160.133
26 2026-08-24 10:41 639231641791249939
2 ms 162.240.160.133
25 2026-08-24 10:25 639231631866211033
342 ms 162.240.160.133
24 2026-08-24 10:08 639231621644955316
335 ms 162.240.160.133
23 2026-08-24 09:51 639231611478799259
345 ms 162.240.160.133
22 2026-08-24 08:59 639231579923718211
340 ms 162.240.160.133
21 2026-08-24 08:42 639231569810702936
357 ms 162.240.160.133
20 2026-08-24 08:25 639231559762411619
2255 ms 162.240.160.133
19 2026-08-24 08:08 639231549663595407
169 ms 162.240.160.133
18 2026-08-24 07:15 639231518076817246
346 ms 162.240.160.133
17 2026-08-24 06:59 639231508078650885
4 ms 162.240.160.133
16 2026-08-24 06:42 639231498210697093
4 ms 162.240.160.133
15 2026-08-24 06:26 639231488109699360
2 ms 162.240.160.133
14 2026-08-24 05:33 639231456772510692
3 ms 162.240.160.133
13 2026-08-24 05:17 639231447084631185
3 ms 162.240.160.133
12 2026-08-24 05:00 639231437208519473
340 ms 162.240.160.133
11 2026-08-24 04:44 639231427209627490
339 ms 162.240.160.133
10 2026-08-24 03:51 639231395791246644
420 ms 162.240.160.133
9 2026-08-24 03:35 639231386075551458
177 ms 162.240.160.133
8 2026-08-24 03:19 639231376208713791
337 ms 162.240.160.133
7 2026-08-24 03:02 639231366170589276
2 ms 162.240.160.133
6 2026-08-24 02:10 639231334732159368
-
5 2026-08-24 01:53 639231325035670078
2 ms 162.240.160.133
4 2026-08-24 01:37 639231315132253837
3 ms 162.240.160.133
3 2026-08-24 01:20 639231305014280808
2008 ms 162.240.160.133
2 2026-08-24 00:28 639231273779380675
3 ms 162.240.160.133
1 2026-08-24 00:12 639231264180839154
384 ms 162.240.160.133