DNS response history for ns.bnfondos.com

ns.bnfondos.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 835 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 ns.bnfondos.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

835 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

201.220.29.22

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 ns.bnfondos.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:09 639231693747052549
752 ms 201.220.29.22
28 2026-08-24 11:52 639231683712487276
733 ms 201.220.29.22
27 2026-08-24 11:35 639231673513573868
426 ms 201.220.29.22
26 2026-08-24 10:42 639231641791249939
357 ms 201.220.29.22
25 2026-08-24 10:26 639231631866211033
749 ms 201.220.29.22
24 2026-08-24 10:09 639231621644955316
5 ms 201.220.29.22
23 2026-08-24 09:52 639231611478799259
747 ms 201.220.29.22
22 2026-08-24 08:59 639231579923718211
5 ms 201.220.29.22
21 2026-08-24 08:43 639231569810702936
4 ms 201.220.29.22
20 2026-08-24 08:26 639231559762411619
722 ms 201.220.29.22
19 2026-08-24 08:09 639231549663595407
750 ms 201.220.29.22
18 2026-08-24 07:16 639231518076817246
505 ms 201.220.29.22
17 2026-08-24 07:00 639231508078650885
362 ms 201.220.29.22
16 2026-08-24 06:43 639231498210697093
758 ms 201.220.29.22
15 2026-08-24 06:26 639231488109699360
736 ms 201.220.29.22
14 2026-08-24 05:34 639231456772510692
3 ms 201.220.29.22
13 2026-08-24 05:18 639231447084631185
367 ms 201.220.29.22
12 2026-08-24 05:01 639231437208519473
732 ms 201.220.29.22
11 2026-08-24 04:45 639231427209627490
3 ms 201.220.29.22
10 2026-08-24 03:52 639231395791246644
355 ms 201.220.29.22
9 2026-08-24 03:36 639231386075551458
880 ms 201.220.29.22
8 2026-08-24 03:20 639231376208713791
2194 ms 201.220.29.22
7 2026-08-24 03:03 639231366170589276
507 ms 201.220.29.22
6 2026-08-24 02:11 639231334732159368
2003 ms 201.220.29.22
5 2026-08-24 01:54 639231325035670078
205 ms 201.220.29.22
4 2026-08-24 01:38 639231315132253837
352 ms 201.220.29.22
3 2026-08-24 01:21 639231305014280808
4739 ms 201.220.29.22
2 2026-08-24 00:29 639231273779380675
716 ms 201.220.29.22
1 2026-08-24 00:13 639231264180839154
3562 ms 201.220.29.22