DNS response history for ns2.hengfam.com

ns2.hengfam.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 329 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 ns2.hengfam.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

329 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

60.241.237.149

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns2.hengfam.com

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:15 639231703815441688
51 ms 60.241.237.149
29 2026-08-24 11:58 639231693747052549
70 ms 60.241.237.149
28 2026-08-24 11:41 639231683712487276
74 ms 60.241.237.149
27 2026-08-24 11:24 639231673513573868
66 ms 60.241.237.149
26 2026-08-24 10:31 639231641791249939
33 ms 60.241.237.149
25 2026-08-24 10:15 639231631866211033
63 ms 60.241.237.149
24 2026-08-24 09:58 639231621644955316
517 ms 60.241.237.149
23 2026-08-24 09:41 639231611478799259
69 ms 60.241.237.149
22 2026-08-24 08:48 639231579923718211
66 ms 60.241.237.149
21 2026-08-24 08:31 639231569810702936
437 ms 60.241.237.149
20 2026-08-24 08:14 639231559762411619
2044 ms 60.241.237.149
19 2026-08-24 07:58 639231549663595407
4049 ms 60.241.237.149
18 2026-08-24 07:05 639231518076817246
43 ms 60.241.237.149
17 2026-08-24 06:48 639231508078650885
304 ms 60.241.237.149
16 2026-08-24 06:32 639231498210697093
66 ms 60.241.237.149
15 2026-08-24 06:15 639231488109699360
264 ms 60.241.237.149
14 2026-08-24 05:23 639231456772510692
544 ms 60.241.237.149
13 2026-08-24 05:07 639231447084631185
51 ms 60.241.237.149
12 2026-08-24 04:50 639231437208519473
31 ms 60.241.237.149
11 2026-08-24 04:34 639231427209627490
45 ms 60.241.237.149
10 2026-08-24 03:41 639231395791246644
340 ms 60.241.237.149
9 2026-08-24 03:25 639231386075551458
44 ms 60.241.237.149
8 2026-08-24 03:09 639231376208713791
297 ms 60.241.237.149
7 2026-08-24 02:52 639231366170589276
48 ms 60.241.237.149
6 2026-08-24 02:00 639231334732159368
52 ms 60.241.237.149
5 2026-08-24 01:43 639231325035670078
36 ms 60.241.237.149
4 2026-08-24 01:27 639231315132253837
46 ms 60.241.237.149
3 2026-08-24 01:10 639231305014280808
45 ms 60.241.237.149
2 2026-08-24 00:18 639231273779380675
41 ms 60.241.237.149
1 2026-08-24 00:02 639231264180839154
46 ms 60.241.237.149