DNS response history for ns1.biperf.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

180 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.246.150.9

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.biperf.com

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 11:34 639233403515141099
255 ms 198.246.150.9
33 2026-08-26 10:40 639233370841350248
274 ms 198.246.150.9
32 2026-08-26 10:22 639233360361507238
153 ms 198.246.150.9
31 2026-08-26 10:05 639233350067824371
125 ms 198.246.150.9
30 2026-08-26 09:48 639233339545274518
271 ms 198.246.150.9
29 2026-08-26 09:30 639233329214918079
258 ms 198.246.150.9
28 2026-08-26 09:13 639233318749762337
136 ms 198.246.150.9
27 2026-08-26 08:56 639233308387917838
8 ms 198.246.150.9
26 2026-08-26 08:38 639233297961740122
226 ms 198.246.150.9
25 2026-08-26 08:21 639233287487159094
140 ms 198.246.150.9
24 2026-08-26 08:04 639233276995531707
143 ms 198.246.150.9
23 2026-08-26 07:46 639233266521568229
257 ms 198.246.150.9
22 2026-08-26 07:29 639233256081047431
252 ms 198.246.150.9
21 2026-08-26 06:35 639233223620132921
9 ms 198.246.150.9
20 2026-08-26 06:17 639233213287814244
182 ms 198.246.150.9
19 2026-08-26 06:00 639233202925983161
255 ms 198.246.150.9
18 2026-08-26 05:43 639233192644780696
278 ms 198.246.150.9
17 2026-08-26 05:26 639233182401183833
261 ms 198.246.150.9
16 2026-08-26 05:09 639233172074181051
265 ms 198.246.150.9
15 2026-08-26 04:51 639233161808421455
256 ms 198.246.150.9
14 2026-08-26 04:34 639233151357344052
255 ms 198.246.150.9
13 2026-08-26 04:17 639233141034116946
255 ms 198.246.150.9
12 2026-08-26 04:00 639233130828334142
10 ms 198.246.150.9
11 2026-08-26 03:43 639233120373450007
4 ms 198.246.150.9
10 2026-08-26 03:25 639233110066216193
127 ms 198.246.150.9
9 2026-08-26 02:32 639233078065410564
256 ms 198.246.150.9
8 2026-08-26 02:15 639233067787457832
3 ms 198.246.150.9
7 2026-08-26 01:58 639233057501801162
257 ms 198.246.150.9
6 2026-08-26 01:40 639233047089431703
258 ms 198.246.150.9
5 2026-08-26 01:23 639233036754790688
7 ms 198.246.150.9
4 2026-08-26 01:06 639233026412602472
257 ms 198.246.150.9
3 2026-08-26 00:48 639233016064066127
128 ms 198.246.150.9
2 2026-08-26 00:31 639233005922655772
156 ms 198.246.150.9
1 2026-08-26 00:14 639232995672256907
149 ms 198.246.150.9