DNS response history for ns1.bilaco.bio

ns1.bilaco.bio 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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 475 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 ns1.bilaco.bio.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

475 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.214.166.78

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 ns1.bilaco.bio

Showing DNS history for 2026-08-26 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-26 10:44 639233370841350248
403 ms 185.214.166.78
33 2026-08-26 10:27 639233360361507238
479 ms 185.214.166.78
32 2026-08-26 10:09 639233350067824371
488 ms 185.214.166.78
31 2026-08-26 09:52 639233339545274518
475 ms 185.214.166.78
30 2026-08-26 09:35 639233329214918079
252 ms 185.214.166.78
29 2026-08-26 09:18 639233318749762337
129 ms 185.214.166.78
28 2026-08-26 09:00 639233308387917838
298 ms 185.214.166.78
27 2026-08-26 08:43 639233297961740122
375 ms 185.214.166.78
26 2026-08-26 08:25 639233287487159094
359 ms 185.214.166.78
25 2026-08-26 08:08 639233276995531707
2287 ms 185.214.166.78
24 2026-08-26 07:50 639233266521568229
361 ms 185.214.166.78
23 2026-08-26 07:33 639233256081047431
432 ms 185.214.166.78
22 2026-08-26 06:39 639233223620132921
362 ms 185.214.166.78
21 2026-08-26 06:22 639233213287814244
241 ms 185.214.166.78
20 2026-08-26 06:04 639233202925983161
382 ms 185.214.166.78
19 2026-08-26 05:47 639233192644780696
426 ms 185.214.166.78
18 2026-08-26 05:30 639233182401183833
364 ms 185.214.166.78
17 2026-08-26 05:13 639233172074181051
487 ms 185.214.166.78
16 2026-08-26 04:56 639233161808421455
372 ms 185.214.166.78
15 2026-08-26 04:39 639233151357344052
235 ms 185.214.166.78
14 2026-08-26 04:21 639233141034116946
230 ms 185.214.166.78
13 2026-08-26 04:04 639233130828334142
357 ms 185.214.166.78
12 2026-08-26 03:47 639233120373450007
234 ms 185.214.166.78
11 2026-08-26 03:29 639233110066216193
369 ms 185.214.166.78
10 2026-08-26 02:36 639233078065410564
414 ms 185.214.166.78
9 2026-08-26 02:19 639233067787457832
398 ms 185.214.166.78
8 2026-08-26 02:02 639233057501801162
226 ms 185.214.166.78
7 2026-08-26 01:45 639233047089431703
243 ms 185.214.166.78
6 2026-08-26 01:27 639233036754790688
625 ms 185.214.166.78
5 2026-08-26 01:10 639233026412602472
360 ms 185.214.166.78
4 2026-08-26 00:53 639233016064066127
2535 ms 185.214.166.78
3 2026-08-26 00:36 639233005922655772
359 ms 185.214.166.78
2 2026-08-26 00:19 639232995672256907
352 ms 185.214.166.78
1 2026-08-26 00:02 639232985300872416
235 ms 185.214.166.78