DNS response history for ns2.balue.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

830 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.222.98.155

Most recently resolved hosting IP on selected date

Successful Responses

29

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.balue.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
29 2026-08-24 12:11 639231693747052549
822 ms 67.222.98.155
28 2026-08-24 11:54 639231683712487276
1299 ms 67.222.98.155
27 2026-08-24 11:37 639231673513573868
303 ms 67.222.98.155
26 2026-08-24 10:44 639231641791249939
1296 ms 67.222.98.155
25 2026-08-24 10:27 639231631866211033
807 ms 67.222.98.155
24 2026-08-24 10:11 639231621644955316
153 ms 67.222.98.155
23 2026-08-24 09:54 639231611478799259
804 ms 67.222.98.155
22 2026-08-24 09:01 639231579923718211
795 ms 67.222.98.155
21 2026-08-24 08:44 639231569810702936
1279 ms 67.222.98.155
20 2026-08-24 08:27 639231559762411619
784 ms 67.222.98.155
19 2026-08-24 08:10 639231549663595407
782 ms 67.222.98.155
18 2026-08-24 07:17 639231518076817246
782 ms 67.222.98.155
17 2026-08-24 07:01 639231508078650885
326 ms 67.222.98.155
16 2026-08-24 06:44 639231498210697093
321 ms 67.222.98.155
15 2026-08-24 06:28 639231488109699360
276 ms 67.222.98.155
14 2026-08-24 05:35 639231456772510692
1541 ms 67.222.98.155
13 2026-08-24 05:19 639231447084631185
1286 ms 67.222.98.155
12 2026-08-24 05:03 639231437208519473
790 ms 67.222.98.155
11 2026-08-24 04:46 639231427209627490
287 ms 67.222.98.155
10 2026-08-24 03:53 639231395791246644
287 ms 67.222.98.155
9 2026-08-24 03:37 639231386075551458
793 ms 67.222.98.155
8 2026-08-24 03:21 639231376208713791
1314 ms 67.222.98.155
7 2026-08-24 03:05 639231366170589276
796 ms 67.222.98.155
6 2026-08-24 02:12 639231334732159368
1712 ms 67.222.98.155
5 2026-08-24 01:56 639231325035670078
1294 ms 67.222.98.155
4 2026-08-24 01:39 639231315132253837
790 ms 67.222.98.155
3 2026-08-24 01:23 639231305014280808
1274 ms 67.222.98.155
2 2026-08-24 00:30 639231273779380675
286 ms 67.222.98.155
1 2026-08-24 00:14 639231264180839154
782 ms 67.222.98.155