DNS response history for m1.hk-compu.com

m1.hk-compu.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 35 DNS check records, 35 successful responses, 0 failed responses, and 342 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 m1.hk-compu.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

342 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.149.240.57

Most recently resolved hosting IP on selected date

Successful Responses

35

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 m1.hk-compu.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
35 2026-08-26 11:39 639233403515141099
197 ms 59.149.240.57
34 2026-08-26 10:44 639233370841350248
197 ms 59.149.240.57
33 2026-08-26 10:27 639233360361507238
184 ms 59.149.240.57
32 2026-08-26 10:09 639233350067824371
188 ms 59.149.240.57
31 2026-08-26 09:52 639233339545274518
371 ms 59.149.240.57
30 2026-08-26 09:35 639233329214918079
393 ms 59.149.240.57
29 2026-08-26 09:18 639233318749762337
774 ms 59.149.240.57
28 2026-08-26 09:00 639233308387917838
188 ms 59.149.240.57
27 2026-08-26 08:43 639233297961740122
372 ms 59.149.240.57
26 2026-08-26 08:25 639233287487159094
459 ms 59.149.240.57
25 2026-08-26 08:08 639233276995531707
224 ms 59.149.240.57
24 2026-08-26 07:50 639233266521568229
188 ms 59.149.240.57
23 2026-08-26 07:33 639233256081047431
372 ms 59.149.240.57
22 2026-08-26 06:39 639233223620132921
188 ms 59.149.240.57
21 2026-08-26 06:22 639233213287814244
190 ms 59.149.240.57
20 2026-08-26 06:04 639233202925983161
372 ms 59.149.240.57
19 2026-08-26 05:47 639233192644780696
220 ms 59.149.240.57
18 2026-08-26 05:30 639233182401183833
187 ms 59.149.240.57
17 2026-08-26 05:13 639233172074181051
373 ms 59.149.240.57
16 2026-08-26 04:56 639233161808421455
186 ms 59.149.240.57
15 2026-08-26 04:39 639233151357344052
938 ms 59.149.240.57
14 2026-08-26 04:21 639233141034116946
3 ms 59.149.240.57
13 2026-08-26 04:04 639233130828334142
370 ms 59.149.240.57
12 2026-08-26 03:47 639233120373450007
196 ms 59.149.240.57
11 2026-08-26 03:29 639233110066216193
373 ms 59.149.240.57
10 2026-08-26 02:36 639233078065410564
3 ms 59.149.240.57
9 2026-08-26 02:19 639233067787457832
371 ms 59.149.240.57
8 2026-08-26 02:02 639233057501801162
3 ms 59.149.240.57
7 2026-08-26 01:45 639233047089431703
187 ms 59.149.240.57
6 2026-08-26 01:27 639233036754790688
379 ms 59.149.240.57
5 2026-08-26 01:10 639233026412602472
372 ms 59.149.240.57
4 2026-08-26 00:53 639233016064066127
368 ms 59.149.240.57
3 2026-08-26 00:36 639233005922655772
195 ms 59.149.240.57
2 2026-08-26 00:19 639232995672256907
2198 ms 59.149.240.57
1 2026-08-26 00:02 639232985300872416
186 ms 59.149.240.57