DNS response history for ns2.banikol.com

ns2.banikol.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 31 DNS check records, 30 successful responses, 1 failed responses, and 98 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.banikol.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

98 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

188.138.29.130

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.banikol.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
31 2026-08-24 13:09 639231735407682062
34 ms 188.138.29.130
30 2026-08-24 12:16 639231703815441688
34 ms 188.138.29.130
29 2026-08-24 11:59 639231693747052549
40 ms 188.138.29.130
28 2026-08-24 11:42 639231683712487276
31 ms 188.138.29.130
27 2026-08-24 11:25 639231673513573868
73 ms 188.138.29.130
26 2026-08-24 10:33 639231641791249939
-
25 2026-08-24 10:16 639231631866211033
73 ms 188.138.29.130
24 2026-08-24 09:59 639231621644955316
34 ms 188.138.29.130
23 2026-08-24 09:42 639231611478799259
10 ms 188.138.29.130
22 2026-08-24 08:50 639231579923718211
77 ms 188.138.29.130
21 2026-08-24 08:33 639231569810702936
32 ms 188.138.29.130
20 2026-08-24 08:16 639231559762411619
34 ms 188.138.29.130
19 2026-08-24 07:59 639231549663595407
13 ms 188.138.29.130
18 2026-08-24 07:06 639231518076817246
41 ms 188.138.29.130
17 2026-08-24 06:50 639231508078650885
29 ms 188.138.29.130
16 2026-08-24 06:33 639231498210697093
12 ms 188.138.29.130
15 2026-08-24 06:16 639231488109699360
41 ms 188.138.29.130
14 2026-08-24 05:24 639231456772510692
3 ms 188.138.29.130
13 2026-08-24 05:08 639231447084631185
3 ms 188.138.29.130
12 2026-08-24 04:52 639231437208519473
16 ms 188.138.29.130
11 2026-08-24 04:35 639231427209627490
28 ms 188.138.29.130
10 2026-08-24 03:43 639231395791246644
36 ms 188.138.29.130
9 2026-08-24 03:26 639231386075551458
30 ms 188.138.29.130
8 2026-08-24 03:10 639231376208713791
11 ms 188.138.29.130
7 2026-08-24 02:53 639231366170589276
32 ms 188.138.29.130
6 2026-08-24 02:01 639231334732159368
19 ms 188.138.29.130
5 2026-08-24 01:45 639231325035670078
3 ms 188.138.29.130
4 2026-08-24 01:28 639231315132253837
30 ms 188.138.29.130
3 2026-08-24 01:11 639231305014280808
2078 ms 188.138.29.130
2 2026-08-24 00:19 639231273779380675
32 ms 188.138.29.130
1 2026-08-24 00:03 639231264180839154
25 ms 188.138.29.130