DNS response history for ns1.hkfirm.net

ns1.hkfirm.net 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 358 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.hkfirm.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

358 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.181.163.150

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.hkfirm.net

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:31 639233434974187439
198 ms 202.181.163.150
37 2026-08-26 12:14 639233424567558554
376 ms 202.181.163.150
36 2026-08-26 11:56 639233414056832719
379 ms 202.181.163.150
35 2026-08-26 11:39 639233403515141099
322 ms 202.181.163.150
34 2026-08-26 10:44 639233370841350248
380 ms 202.181.163.150
33 2026-08-26 10:27 639233360361507238
383 ms 202.181.163.150
32 2026-08-26 10:10 639233350067824371
382 ms 202.181.163.150
31 2026-08-26 09:52 639233339545274518
380 ms 202.181.163.150
30 2026-08-26 09:35 639233329214918079
378 ms 202.181.163.150
29 2026-08-26 09:18 639233318749762337
384 ms 202.181.163.150
28 2026-08-26 09:00 639233308387917838
388 ms 202.181.163.150
27 2026-08-26 08:43 639233297961740122
394 ms 202.181.163.150
26 2026-08-26 08:26 639233287487159094
382 ms 202.181.163.150
25 2026-08-26 08:08 639233276995531707
393 ms 202.181.163.150
24 2026-08-26 07:51 639233266521568229
390 ms 202.181.163.150
23 2026-08-26 07:33 639233256081047431
203 ms 202.181.163.150
22 2026-08-26 06:39 639233223620132921
401 ms 202.181.163.150
21 2026-08-26 06:22 639233213287814244
420 ms 202.181.163.150
20 2026-08-26 06:04 639233202925983161
376 ms 202.181.163.150
19 2026-08-26 05:47 639233192644780696
379 ms 202.181.163.150
18 2026-08-26 05:30 639233182401183833
378 ms 202.181.163.150
17 2026-08-26 05:13 639233172074181051
378 ms 202.181.163.150
16 2026-08-26 04:56 639233161808421455
380 ms 202.181.163.150
15 2026-08-26 04:39 639233151357344052
379 ms 202.181.163.150
14 2026-08-26 04:21 639233141034116946
381 ms 202.181.163.150
13 2026-08-26 04:04 639233130828334142
381 ms 202.181.163.150
12 2026-08-26 03:47 639233120373450007
381 ms 202.181.163.150
11 2026-08-26 03:30 639233110066216193
378 ms 202.181.163.150
10 2026-08-26 02:36 639233078065410564
380 ms 202.181.163.150
9 2026-08-26 02:19 639233067787457832
398 ms 202.181.163.150
8 2026-08-26 02:02 639233057501801162
375 ms 202.181.163.150
7 2026-08-26 01:45 639233047089431703
9 ms 202.181.163.150
6 2026-08-26 01:28 639233036754790688
379 ms 202.181.163.150
5 2026-08-26 01:10 639233026412602472
379 ms 202.181.163.150
4 2026-08-26 00:53 639233016064066127
382 ms 202.181.163.150
3 2026-08-26 00:36 639233005922655772
210 ms 202.181.163.150
2 2026-08-26 00:19 639232995672256907
384 ms 202.181.163.150
1 2026-08-26 00:02 639232985300872416
380 ms 202.181.163.150