DNS response history for ns2.basemind.tech

ns2.basemind.tech 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 37 DNS check records, 37 successful responses, 0 failed responses, and 347 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.basemind.tech.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

80.78.246.153

Most recently resolved hosting IP on selected date

Successful Responses

37

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.basemind.tech

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
37 2026-08-24 15:32 639231818080917481
3 ms 80.78.246.153
36 2026-08-24 15:14 639231807961539652
5 ms 80.78.246.153
35 2026-08-24 14:58 639231797631669865
105 ms 80.78.246.153
34 2026-08-24 14:05 639231765923559455
8 ms 80.78.246.153
33 2026-08-24 13:48 639231755868832964
7 ms 80.78.246.153
32 2026-08-24 13:31 639231745628278877
66 ms 80.78.246.153
31 2026-08-24 13:14 639231735407682062
286 ms 80.78.246.153
30 2026-08-24 12:21 639231703815441688
6 ms 80.78.246.153
29 2026-08-24 12:04 639231693747052549
71 ms 80.78.246.153
28 2026-08-24 11:47 639231683712487276
196 ms 80.78.246.153
27 2026-08-24 11:31 639231673513573868
90 ms 80.78.246.153
26 2026-08-24 10:38 639231641791249939
52 ms 80.78.246.153
25 2026-08-24 10:21 639231631866211033
87 ms 80.78.246.153
24 2026-08-24 10:04 639231621644955316
2114 ms 80.78.246.153
23 2026-08-24 09:47 639231611478799259
114 ms 80.78.246.153
22 2026-08-24 08:55 639231579923718211
107 ms 80.78.246.153
21 2026-08-24 08:38 639231569810702936
119 ms 80.78.246.153
20 2026-08-24 08:21 639231559762411619
87 ms 80.78.246.153
19 2026-08-24 08:04 639231549663595407
5 ms 80.78.246.153
18 2026-08-24 07:12 639231518076817246
117 ms 80.78.246.153
17 2026-08-24 06:55 639231508078650885
7 ms 80.78.246.153
16 2026-08-24 06:38 639231498210697093
74 ms 80.78.246.153
15 2026-08-24 06:22 639231488109699360
50 ms 80.78.246.153
14 2026-08-24 05:30 639231456772510692
2118 ms 80.78.246.153
13 2026-08-24 05:13 639231447084631185
3 ms 80.78.246.153
12 2026-08-24 04:57 639231437208519473
107 ms 80.78.246.153
11 2026-08-24 04:40 639231427209627490
7 ms 80.78.246.153
10 2026-08-24 03:48 639231395791246644
74 ms 80.78.246.153
9 2026-08-24 03:32 639231386075551458
128 ms 80.78.246.153
8 2026-08-24 03:15 639231376208713791
3 ms 80.78.246.153
7 2026-08-24 02:58 639231366170589276
117 ms 80.78.246.153
6 2026-08-24 02:06 639231334732159368
108 ms 80.78.246.153
5 2026-08-24 01:50 639231325035670078
4086 ms 80.78.246.153
4 2026-08-24 01:33 639231315132253837
116 ms 80.78.246.153
3 2026-08-24 01:17 639231305014280808
2061 ms 80.78.246.153
2 2026-08-24 00:24 639231273779380675
131 ms 80.78.246.153
1 2026-08-24 00:08 639231264180839154
7 ms 80.78.246.153