DNS response history for ns2.balhath.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.53.147.122

Most recently resolved hosting IP on selected date

Successful Responses

32

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.balhath.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
32 2026-08-24 13:33 639231745628278877
306 ms 101.53.147.122
31 2026-08-24 13:15 639231735407682062
302 ms 101.53.147.122
30 2026-08-24 12:23 639231703815441688
33 ms 101.53.147.122
29 2026-08-24 12:06 639231693747052549
317 ms 101.53.147.122
28 2026-08-24 11:49 639231683712487276
2206 ms 101.53.147.122
27 2026-08-24 11:32 639231673513573868
322 ms 101.53.147.122
26 2026-08-24 10:39 639231641791249939
310 ms 101.53.147.122
25 2026-08-24 10:23 639231631866211033
195 ms 101.53.147.122
24 2026-08-24 10:06 639231621644955316
7 ms 101.53.147.122
23 2026-08-24 09:49 639231611478799259
5 ms 101.53.147.122
22 2026-08-24 08:57 639231579923718211
317 ms 101.53.147.122
21 2026-08-24 08:40 639231569810702936
211 ms 101.53.147.122
20 2026-08-24 08:23 639231559762411619
261 ms 101.53.147.122
19 2026-08-24 08:06 639231549663595407
318 ms 101.53.147.122
18 2026-08-24 07:13 639231518076817246
324 ms 101.53.147.122
17 2026-08-24 06:57 639231508078650885
325 ms 101.53.147.122
16 2026-08-24 06:40 639231498210697093
316 ms 101.53.147.122
15 2026-08-24 06:24 639231488109699360
2217 ms 101.53.147.122
14 2026-08-24 05:31 639231456772510692
173 ms 101.53.147.122
13 2026-08-24 05:15 639231447084631185
406 ms 101.53.147.122
12 2026-08-24 04:58 639231437208519473
314 ms 101.53.147.122
11 2026-08-24 04:42 639231427209627490
303 ms 101.53.147.122
10 2026-08-24 03:49 639231395791246644
9 ms 101.53.147.122
9 2026-08-24 03:33 639231386075551458
15 ms 101.53.147.122
8 2026-08-24 03:17 639231376208713791
7 ms 101.53.147.122
7 2026-08-24 03:00 639231366170589276
310 ms 101.53.147.122
6 2026-08-24 02:08 639231334732159368
319 ms 101.53.147.122
5 2026-08-24 01:51 639231325035670078
309 ms 101.53.147.122
4 2026-08-24 01:35 639231315132253837
197 ms 101.53.147.122
3 2026-08-24 01:18 639231305014280808
5 ms 101.53.147.122
2 2026-08-24 00:26 639231273779380675
14 ms 101.53.147.122
1 2026-08-24 00:10 639231264180839154
2397 ms 101.53.147.122