DNS response history for ns1.digitalhooman.net

ns1.digitalhooman.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 28 DNS check records, 28 successful responses, 0 failed responses, and 353 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.digitalhooman.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

353 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.86.116.220

Most recently resolved hosting IP on selected date

Successful Responses

28

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.digitalhooman.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
28 2026-08-26 09:10 639233318749762337
2358 ms 167.86.116.220
27 2026-08-26 08:52 639233308387917838
46 ms 167.86.116.220
26 2026-08-26 08:35 639233297961740122
48 ms 167.86.116.220
25 2026-08-26 08:18 639233287487159094
64 ms 167.86.116.220
24 2026-08-26 08:00 639233276995531707
62 ms 167.86.116.220
23 2026-08-26 07:43 639233266521568229
2061 ms 167.86.116.220
22 2026-08-26 07:25 639233256081047431
59 ms 167.86.116.220
21 2026-08-26 06:31 639233223620132921
2051 ms 167.86.116.220
20 2026-08-26 06:14 639233213287814244
37 ms 167.86.116.220
19 2026-08-26 05:57 639233202925983161
36 ms 167.86.116.220
18 2026-08-26 05:39 639233192644780696
46 ms 167.86.116.220
17 2026-08-26 05:22 639233182401183833
31 ms 167.86.116.220
16 2026-08-26 05:05 639233172074181051
59 ms 167.86.116.220
15 2026-08-26 04:48 639233161808421455
124 ms 167.86.116.220
14 2026-08-26 04:31 639233151357344052
85 ms 167.86.116.220
13 2026-08-26 04:14 639233141034116946
58 ms 167.86.116.220
12 2026-08-26 03:56 639233130828334142
43 ms 167.86.116.220
11 2026-08-26 03:39 639233120373450007
16 ms 167.86.116.220
10 2026-08-26 03:22 639233110066216193
45 ms 167.86.116.220
9 2026-08-26 02:29 639233078065410564
14 ms 167.86.116.220
8 2026-08-26 02:11 639233067787457832
84 ms 167.86.116.220
7 2026-08-26 01:54 639233057501801162
88 ms 167.86.116.220
6 2026-08-26 01:37 639233047089431703
7 ms 167.86.116.220
5 2026-08-26 01:20 639233036754790688
48 ms 167.86.116.220
4 2026-08-26 01:02 639233026412602472
56 ms 167.86.116.220
3 2026-08-26 00:45 639233016064066127
123 ms 167.86.116.220
2 2026-08-26 00:28 639233005922655772
2052 ms 167.86.116.220
1 2026-08-26 00:11 639232995672256907
84 ms 167.86.116.220