DNS response history for ns1.nft2bc.com

ns1.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-30. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 293 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 ns1.nft2bc.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

293 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:29

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

31

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 ns1.nft2bc.com

Showing DNS history for 2026-08-30 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
31 2026-08-30 10:29 639236817708615077
359 ms 162.240.160.133
30 2026-08-30 09:35 639236785770651804
174 ms 162.240.160.133
29 2026-08-30 09:19 639236775820686373
5 ms 162.240.160.133
28 2026-08-30 09:02 639236765768339082
174 ms 162.240.160.133
27 2026-08-30 08:45 639236755602384085
344 ms 162.240.160.133
26 2026-08-30 08:28 639236745600094925
347 ms 162.240.160.133
25 2026-08-30 08:12 639236735311262753
346 ms 162.240.160.133
24 2026-08-30 07:54 639236724996745235
346 ms 162.240.160.133
23 2026-08-30 07:37 639236714839899761
350 ms 162.240.160.133
22 2026-08-30 07:20 639236704748431488
177 ms 162.240.160.133
21 2026-08-30 07:03 639236694430128550
347 ms 162.240.160.133
20 2026-08-30 06:46 639236684143292417
351 ms 162.240.160.133
19 2026-08-30 06:29 639236673972499943
350 ms 162.240.160.133
18 2026-08-30 05:36 639236642126522802
345 ms 162.240.160.133
17 2026-08-30 05:19 639236632183518198
349 ms 162.240.160.133
16 2026-08-30 05:03 639236622289312589
175 ms 162.240.160.133
15 2026-08-30 04:46 639236612490676525
174 ms 162.240.160.133
14 2026-08-30 04:30 639236602582494852
348 ms 162.240.160.133
13 2026-08-30 04:13 639236592511706469
2 ms 162.240.160.133
12 2026-08-30 03:57 639236582441006869
354 ms 162.240.160.133
11 2026-08-30 03:40 639236572478785089
346 ms 162.240.160.133
10 2026-08-30 03:23 639236562556749999
350 ms 162.240.160.133
9 2026-08-30 03:07 639236552353482281
349 ms 162.240.160.133
8 2026-08-30 02:49 639236542188881607
352 ms 162.240.160.133
7 2026-08-30 02:32 639236531885440105
346 ms 162.240.160.133
6 2026-08-30 01:39 639236499922985383
351 ms 162.240.160.133
5 2026-08-30 01:22 639236489713594431
352 ms 162.240.160.133
4 2026-08-30 01:05 639236479750443901
173 ms 162.240.160.133
3 2026-08-30 00:49 639236469719936375
348 ms 162.240.160.133
2 2026-08-30 00:32 639236459579244885
346 ms 162.240.160.133
1 2026-08-30 00:15 639236449582837549
365 ms 162.240.160.133