DNS response history for ns1.biofy.link

ns1.biofy.link 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 38 DNS check records, 38 successful responses, 0 failed responses, and 536 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.biofy.link.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

536 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.99.37.202

Most recently resolved hosting IP on selected date

Successful Responses

38

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.biofy.link

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
38 2026-08-26 12:30 639233434974187439
346 ms 103.99.37.202
37 2026-08-26 12:13 639233424567558554
345 ms 103.99.37.202
36 2026-08-26 11:55 639233414056832719
377 ms 103.99.37.202
35 2026-08-26 11:38 639233403515141099
386 ms 103.99.37.202
34 2026-08-26 10:43 639233370841350248
360 ms 103.99.37.202
33 2026-08-26 10:26 639233360361507238
380 ms 103.99.37.202
32 2026-08-26 10:09 639233350067824371
380 ms 103.99.37.202
31 2026-08-26 09:51 639233339545274518
339 ms 103.99.37.202
30 2026-08-26 09:34 639233329214918079
371 ms 103.99.37.202
29 2026-08-26 09:17 639233318749762337
295 ms 103.99.37.202
28 2026-08-26 08:59 639233308387917838
360 ms 103.99.37.202
27 2026-08-26 08:42 639233297961740122
394 ms 103.99.37.202
26 2026-08-26 08:24 639233287487159094
2231 ms 103.99.37.202
25 2026-08-26 08:07 639233276995531707
393 ms 103.99.37.202
24 2026-08-26 07:49 639233266521568229
327 ms 103.99.37.202
23 2026-08-26 07:32 639233256081047431
286 ms 103.99.37.202
22 2026-08-26 06:38 639233223620132921
279 ms 103.99.37.202
21 2026-08-26 06:21 639233213287814244
4 ms 103.99.37.202
20 2026-08-26 06:03 639233202925983161
338 ms 103.99.37.202
19 2026-08-26 05:46 639233192644780696
380 ms 103.99.37.202
18 2026-08-26 05:29 639233182401183833
374 ms 103.99.37.202
17 2026-08-26 05:12 639233172074181051
384 ms 103.99.37.202
16 2026-08-26 04:55 639233161808421455
361 ms 103.99.37.202
15 2026-08-26 04:38 639233151357344052
311 ms 103.99.37.202
14 2026-08-26 04:20 639233141034116946
257 ms 103.99.37.202
13 2026-08-26 04:03 639233130828334142
322 ms 103.99.37.202
12 2026-08-26 03:46 639233120373450007
4387 ms 103.99.37.202
11 2026-08-26 03:28 639233110066216193
362 ms 103.99.37.202
10 2026-08-26 02:35 639233078065410564
352 ms 103.99.37.202
9 2026-08-26 02:18 639233067787457832
323 ms 103.99.37.202
8 2026-08-26 02:01 639233057501801162
281 ms 103.99.37.202
7 2026-08-26 01:44 639233047089431703
2008 ms 103.99.37.202
6 2026-08-26 01:26 639233036754790688
280 ms 103.99.37.202
5 2026-08-26 01:09 639233026412602472
335 ms 103.99.37.202
4 2026-08-26 00:52 639233016064066127
331 ms 103.99.37.202
3 2026-08-26 00:35 639233005922655772
393 ms 103.99.37.202
2 2026-08-26 00:18 639232995672256907
379 ms 103.99.37.202
1 2026-08-26 00:01 639232985300872416
375 ms 103.99.37.202