DNS response history for ns2.baneandox.com

ns2.baneandox.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 34 DNS check records, 34 successful responses, 0 failed responses, and 671 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.baneandox.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

671 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

144.121.7.137

Most recently resolved hosting IP on selected date

Successful Responses

34

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.baneandox.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
34 2026-08-24 14:08 639231765923559455
3 ms 144.121.7.137
33 2026-08-24 13:52 639231755868832964
855 ms 144.121.7.137
32 2026-08-24 13:35 639231745628278877
2 ms 144.121.7.137
31 2026-08-24 13:17 639231735407682062
849 ms 144.121.7.137
30 2026-08-24 12:25 639231703815441688
871 ms 144.121.7.137
29 2026-08-24 12:08 639231693747052549
402 ms 144.121.7.137
28 2026-08-24 11:51 639231683712487276
2951 ms 144.121.7.137
27 2026-08-24 11:34 639231673513573868
850 ms 144.121.7.137
26 2026-08-24 10:41 639231641791249939
5 ms 144.121.7.137
25 2026-08-24 10:25 639231631866211033
1226 ms 144.121.7.137
24 2026-08-24 10:08 639231621644955316
863 ms 144.121.7.137
23 2026-08-24 09:51 639231611478799259
864 ms 144.121.7.137
22 2026-08-24 08:58 639231579923718211
872 ms 144.121.7.137
21 2026-08-24 08:42 639231569810702936
102 ms 144.121.7.137
20 2026-08-24 08:25 639231559762411619
866 ms 144.121.7.137
19 2026-08-24 08:08 639231549663595407
3 ms 144.121.7.137
18 2026-08-24 07:15 639231518076817246
5 ms 144.121.7.137
17 2026-08-24 06:59 639231508078650885
101 ms 144.121.7.137
16 2026-08-24 06:42 639231498210697093
854 ms 144.121.7.137
15 2026-08-24 06:26 639231488109699360
1699 ms 144.121.7.137
14 2026-08-24 05:33 639231456772510692
864 ms 144.121.7.137
13 2026-08-24 05:17 639231447084631185
1709 ms 144.121.7.137
12 2026-08-24 05:00 639231437208519473
395 ms 144.121.7.137
11 2026-08-24 04:44 639231427209627490
262 ms 144.121.7.137
10 2026-08-24 03:51 639231395791246644
103 ms 144.121.7.137
9 2026-08-24 03:35 639231386075551458
28 ms 144.121.7.137
8 2026-08-24 03:19 639231376208713791
4 ms 144.121.7.137
7 2026-08-24 03:02 639231366170589276
4 ms 144.121.7.137
6 2026-08-24 02:10 639231334732159368
856 ms 144.121.7.137
5 2026-08-24 01:53 639231325035670078
1790 ms 144.121.7.137
4 2026-08-24 01:37 639231315132253837
2 ms 144.121.7.137
3 2026-08-24 01:20 639231305014280808
396 ms 144.121.7.137
2 2026-08-24 00:28 639231273779380675
2149 ms 144.121.7.137
1 2026-08-24 00:12 639231264180839154
7 ms 144.121.7.137