DNS response history for ns2.balli.com

ns2.balli.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 516 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.balli.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

516 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.188.225

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.balli.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 11:58 639231693747052549
43 ms 67.225.188.225
28 2026-08-24 11:42 639231683712487276
627 ms 67.225.188.225
27 2026-08-24 11:25 639231673513573868
55 ms 67.225.188.225
26 2026-08-24 10:32 639231641791249939
21 ms 67.225.188.225
25 2026-08-24 10:15 639231631866211033
40 ms 67.225.188.225
24 2026-08-24 09:58 639231621644955316
71 ms 67.225.188.225
23 2026-08-24 09:41 639231611478799259
43 ms 67.225.188.225
22 2026-08-24 08:49 639231579923718211
99 ms 67.225.188.225
21 2026-08-24 08:32 639231569810702936
31 ms 67.225.188.225
20 2026-08-24 08:15 639231559762411619
28 ms 67.225.188.225
19 2026-08-24 07:58 639231549663595407
38 ms 67.225.188.225
18 2026-08-24 07:06 639231518076817246
34 ms 67.225.188.225
17 2026-08-24 06:49 639231508078650885
62 ms 67.225.188.225
16 2026-08-24 06:33 639231498210697093
61 ms 67.225.188.225
15 2026-08-24 06:16 639231488109699360
66 ms 67.225.188.225
14 2026-08-24 05:23 639231456772510692
2061 ms 67.225.188.225
13 2026-08-24 05:07 639231447084631185
41 ms 67.225.188.225
12 2026-08-24 04:51 639231437208519473
2178 ms 67.225.188.225
11 2026-08-24 04:34 639231427209627490
595 ms 67.225.188.225
10 2026-08-24 03:42 639231395791246644
31 ms 67.225.188.225
9 2026-08-24 03:26 639231386075551458
2038 ms 67.225.188.225
8 2026-08-24 03:09 639231376208713791
47 ms 67.225.188.225
7 2026-08-24 02:52 639231366170589276
2027 ms 67.225.188.225
6 2026-08-24 02:00 639231334732159368
2440 ms 67.225.188.225
5 2026-08-24 01:44 639231325035670078
39 ms 67.225.188.225
4 2026-08-24 01:27 639231315132253837
76 ms 67.225.188.225
3 2026-08-24 01:11 639231305014280808
38 ms 67.225.188.225
2 2026-08-24 00:19 639231273779380675
22 ms 67.225.188.225
1 2026-08-24 00:02 639231264180839154
2014 ms 67.225.188.225