DNS response history for ns1.bhl.com.hk

ns1.bhl.com.hk 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 36 DNS check records, 36 successful responses, 0 failed responses, and 523 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.bhl.com.hk.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

523 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.15.132.122

Most recently resolved hosting IP on selected date

Successful Responses

36

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.bhl.com.hk

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
36 2026-08-26 11:56 639233414056832719
717 ms 103.15.132.122
35 2026-08-26 11:38 639233403515141099
484 ms 103.15.132.122
34 2026-08-26 10:44 639233370841350248
240 ms 103.15.132.122
33 2026-08-26 10:26 639233360361507238
467 ms 103.15.132.122
32 2026-08-26 10:09 639233350067824371
481 ms 103.15.132.122
31 2026-08-26 09:52 639233339545274518
239 ms 103.15.132.122
30 2026-08-26 09:34 639233329214918079
238 ms 103.15.132.122
29 2026-08-26 09:17 639233318749762337
233 ms 103.15.132.122
28 2026-08-26 09:00 639233308387917838
477 ms 103.15.132.122
27 2026-08-26 08:42 639233297961740122
234 ms 103.15.132.122
26 2026-08-26 08:25 639233287487159094
465 ms 103.15.132.122
25 2026-08-26 08:08 639233276995531707
479 ms 103.15.132.122
24 2026-08-26 07:50 639233266521568229
781 ms 103.15.132.122
23 2026-08-26 07:32 639233256081047431
237 ms 103.15.132.122
22 2026-08-26 06:39 639233223620132921
241 ms 103.15.132.122
21 2026-08-26 06:21 639233213287814244
475 ms 103.15.132.122
20 2026-08-26 06:04 639233202925983161
478 ms 103.15.132.122
19 2026-08-26 05:47 639233192644780696
239 ms 103.15.132.122
18 2026-08-26 05:29 639233182401183833
233 ms 103.15.132.122
17 2026-08-26 05:13 639233172074181051
470 ms 103.15.132.122
16 2026-08-26 04:55 639233161808421455
2020 ms 103.15.132.122
15 2026-08-26 04:38 639233151357344052
767 ms 103.15.132.122
14 2026-08-26 04:21 639233141034116946
238 ms 103.15.132.122
13 2026-08-26 04:04 639233130828334142
477 ms 103.15.132.122
12 2026-08-26 03:46 639233120373450007
476 ms 103.15.132.122
11 2026-08-26 03:29 639233110066216193
2260 ms 103.15.132.122
10 2026-08-26 02:36 639233078065410564
234 ms 103.15.132.122
9 2026-08-26 02:19 639233067787457832
247 ms 103.15.132.122
8 2026-08-26 02:01 639233057501801162
469 ms 103.15.132.122
7 2026-08-26 01:44 639233047089431703
2289 ms 103.15.132.122
6 2026-08-26 01:27 639233036754790688
4 ms 103.15.132.122
5 2026-08-26 01:10 639233026412602472
242 ms 103.15.132.122
4 2026-08-26 00:52 639233016064066127
239 ms 103.15.132.122
3 2026-08-26 00:35 639233005922655772
257 ms 103.15.132.122
2 2026-08-26 00:18 639232995672256907
237 ms 103.15.132.122
1 2026-08-26 00:01 639232985300872416
470 ms 103.15.132.122