DNS response history for ns1.bikingbee.com

ns1.bikingbee.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 37 DNS check records, 37 successful responses, 0 failed responses, and 190 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.bikingbee.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

190 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.167.202.146

Most recently resolved hosting IP on selected date

Successful Responses

37

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.bikingbee.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
37 2026-08-26 12:17 639233424567558554
345 ms 199.167.202.146
36 2026-08-26 11:59 639233414056832719
300 ms 199.167.202.146
35 2026-08-26 11:42 639233403515141099
153 ms 199.167.202.146
34 2026-08-26 10:47 639233370841350248
152 ms 199.167.202.146
33 2026-08-26 10:30 639233360361507238
305 ms 199.167.202.146
32 2026-08-26 10:12 639233350067824371
3 ms 199.167.202.146
31 2026-08-26 09:55 639233339545274518
309 ms 199.167.202.146
30 2026-08-26 09:37 639233329214918079
4 ms 199.167.202.146
29 2026-08-26 09:20 639233318749762337
298 ms 199.167.202.146
28 2026-08-26 09:03 639233308387917838
160 ms 199.167.202.146
27 2026-08-26 08:46 639233297961740122
321 ms 199.167.202.146
26 2026-08-26 08:28 639233287487159094
155 ms 199.167.202.146
25 2026-08-26 08:11 639233276995531707
151 ms 199.167.202.146
24 2026-08-26 07:53 639233266521568229
362 ms 199.167.202.146
23 2026-08-26 07:36 639233256081047431
326 ms 199.167.202.146
22 2026-08-26 06:42 639233223620132921
149 ms 199.167.202.146
21 2026-08-26 06:24 639233213287814244
4 ms 199.167.202.146
20 2026-08-26 06:07 639233202925983161
3 ms 199.167.202.146
19 2026-08-26 05:50 639233192644780696
151 ms 199.167.202.146
18 2026-08-26 05:33 639233182401183833
148 ms 199.167.202.146
17 2026-08-26 05:16 639233172074181051
358 ms 199.167.202.146
16 2026-08-26 04:58 639233161808421455
298 ms 199.167.202.146
15 2026-08-26 04:41 639233151357344052
298 ms 199.167.202.146
14 2026-08-26 04:24 639233141034116946
317 ms 199.167.202.146
13 2026-08-26 04:07 639233130828334142
154 ms 199.167.202.146
12 2026-08-26 03:50 639233120373450007
3 ms 199.167.202.146
11 2026-08-26 03:32 639233110066216193
2 ms 199.167.202.146
10 2026-08-26 02:39 639233078065410564
151 ms 199.167.202.146
9 2026-08-26 02:22 639233067787457832
322 ms 199.167.202.146
8 2026-08-26 02:05 639233057501801162
3 ms 199.167.202.146
7 2026-08-26 01:47 639233047089431703
353 ms 199.167.202.146
6 2026-08-26 01:30 639233036754790688
152 ms 199.167.202.146
5 2026-08-26 01:13 639233026412602472
343 ms 199.167.202.146
4 2026-08-26 00:56 639233016064066127
153 ms 199.167.202.146
3 2026-08-26 00:38 639233005922655772
314 ms 199.167.202.146
2 2026-08-26 00:21 639232995672256907
3 ms 199.167.202.146
1 2026-08-26 00:04 639232985300872416
2 ms 199.167.202.146