DNS response history for ns.bioav.com

ns.bioav.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 34 DNS check records, 34 successful responses, 0 failed responses, and 414 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.bioav.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.136.122.54

Most recently resolved hosting IP on selected date

Successful Responses

34

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.bioav.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
34 2026-08-24 14:09 639231765923559455
4 ms 125.136.122.54
33 2026-08-24 13:52 639231755868832964
574 ms 125.136.122.54
32 2026-08-24 13:35 639231745628278877
584 ms 125.136.122.54
31 2026-08-24 13:18 639231735407682062
2 ms 125.136.122.54
30 2026-08-24 12:25 639231703815441688
3 ms 125.136.122.54
29 2026-08-24 12:09 639231693747052549
4 ms 125.136.122.54
28 2026-08-24 11:52 639231683712487276
591 ms 125.136.122.54
27 2026-08-24 11:35 639231673513573868
4 ms 125.136.122.54
26 2026-08-24 10:42 639231641791249939
4 ms 125.136.122.54
25 2026-08-24 10:26 639231631866211033
563 ms 125.136.122.54
24 2026-08-24 10:09 639231621644955316
3 ms 125.136.122.54
23 2026-08-24 09:52 639231611478799259
3 ms 125.136.122.54
22 2026-08-24 08:59 639231579923718211
2007 ms 125.136.122.54
21 2026-08-24 08:42 639231569810702936
583 ms 125.136.122.54
20 2026-08-24 08:25 639231559762411619
584 ms 125.136.122.54
19 2026-08-24 08:09 639231549663595407
564 ms 125.136.122.54
18 2026-08-24 07:16 639231518076817246
358 ms 125.136.122.54
17 2026-08-24 06:59 639231508078650885
4 ms 125.136.122.54
16 2026-08-24 06:43 639231498210697093
578 ms 125.136.122.54
15 2026-08-24 06:26 639231488109699360
587 ms 125.136.122.54
14 2026-08-24 05:34 639231456772510692
4 ms 125.136.122.54
13 2026-08-24 05:17 639231447084631185
586 ms 125.136.122.54
12 2026-08-24 05:01 639231437208519473
4 ms 125.136.122.54
11 2026-08-24 04:44 639231427209627490
4 ms 125.136.122.54
10 2026-08-24 03:52 639231395791246644
3 ms 125.136.122.54
9 2026-08-24 03:36 639231386075551458
2 ms 125.136.122.54
8 2026-08-24 03:20 639231376208713791
585 ms 125.136.122.54
7 2026-08-24 03:03 639231366170589276
11 ms 125.136.122.54
6 2026-08-24 02:10 639231334732159368
597 ms 125.136.122.54
5 2026-08-24 01:54 639231325035670078
3 ms 125.136.122.54
4 2026-08-24 01:38 639231315132253837
2010 ms 125.136.122.54
3 2026-08-24 01:21 639231305014280808
326 ms 125.136.122.54
2 2026-08-24 00:28 639231273779380675
3 ms 125.136.122.54
1 2026-08-24 00:13 639231264180839154
2324 ms 125.136.122.54