DNS response history for ns2.hihompy.com

ns2.hihompy.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 34 DNS check records, 34 successful responses, 0 failed responses, and 438 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.hihompy.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

438 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

114.108.129.179

Most recently resolved hosting IP on selected date

Successful Responses

34

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.hihompy.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
34 2026-08-26 10:45 639233370841350248
291 ms 114.108.129.179
33 2026-08-26 10:28 639233360361507238
292 ms 114.108.129.179
32 2026-08-26 10:10 639233350067824371
577 ms 114.108.129.179
31 2026-08-26 09:53 639233339545274518
300 ms 114.108.129.179
30 2026-08-26 09:36 639233329214918079
581 ms 114.108.129.179
29 2026-08-26 09:18 639233318749762337
4 ms 114.108.129.179
28 2026-08-26 09:01 639233308387917838
587 ms 114.108.129.179
27 2026-08-26 08:44 639233297961740122
606 ms 114.108.129.179
26 2026-08-26 08:26 639233287487159094
609 ms 114.108.129.179
25 2026-08-26 08:09 639233276995531707
625 ms 114.108.129.179
24 2026-08-26 07:51 639233266521568229
609 ms 114.108.129.179
23 2026-08-26 07:34 639233256081047431
299 ms 114.108.129.179
22 2026-08-26 06:40 639233223620132921
323 ms 114.108.129.179
21 2026-08-26 06:22 639233213287814244
591 ms 114.108.129.179
20 2026-08-26 06:05 639233202925983161
619 ms 114.108.129.179
19 2026-08-26 05:48 639233192644780696
314 ms 114.108.129.179
18 2026-08-26 05:31 639233182401183833
596 ms 114.108.129.179
17 2026-08-26 05:14 639233172074181051
3 ms 114.108.129.179
16 2026-08-26 04:56 639233161808421455
598 ms 114.108.129.179
15 2026-08-26 04:39 639233151357344052
616 ms 114.108.129.179
14 2026-08-26 04:22 639233141034116946
609 ms 114.108.129.179
13 2026-08-26 04:05 639233130828334142
717 ms 114.108.129.179
12 2026-08-26 03:48 639233120373450007
606 ms 114.108.129.179
11 2026-08-26 03:30 639233110066216193
312 ms 114.108.129.179
10 2026-08-26 02:37 639233078065410564
607 ms 114.108.129.179
9 2026-08-26 02:20 639233067787457832
300 ms 114.108.129.179
8 2026-08-26 02:03 639233057501801162
296 ms 114.108.129.179
7 2026-08-26 01:46 639233047089431703
296 ms 114.108.129.179
6 2026-08-26 01:28 639233036754790688
294 ms 114.108.129.179
5 2026-08-26 01:11 639233026412602472
286 ms 114.108.129.179
4 2026-08-26 00:54 639233016064066127
613 ms 114.108.129.179
3 2026-08-26 00:37 639233005922655772
297 ms 114.108.129.179
2 2026-08-26 00:20 639232995672256907
312 ms 114.108.129.179
1 2026-08-26 00:02 639232985300872416
308 ms 114.108.129.179