DNS response history for ns2.hohertz.net

ns2.hohertz.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 26 DNS check records, 26 successful responses, 0 failed responses, and 175 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.hohertz.net.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

175 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 04:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.11.168.168

Most recently resolved hosting IP on selected date

Successful Responses

26

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.hohertz.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
26 2026-08-26 04:08 639233141034116946
45 ms 52.11.168.168
25 2026-08-26 04:08 639233141034116946
45 ms 205.251.197.65
24 2026-08-26 03:51 639233130828334142
14 ms 205.251.197.65
23 2026-08-26 03:51 639233130828334142
14 ms 52.11.168.168
22 2026-08-26 03:34 639233120373450007
2010 ms 205.251.197.65
21 2026-08-26 03:34 639233120373450007
2010 ms 52.11.168.168
20 2026-08-26 03:17 639233110066216193
21 ms 205.251.197.65
19 2026-08-26 03:17 639233110066216193
21 ms 52.11.168.168
18 2026-08-26 02:23 639233078065410564
16 ms 205.251.197.65
17 2026-08-26 02:23 639233078065410564
16 ms 52.11.168.168
16 2026-08-26 02:06 639233067787457832
33 ms 52.11.168.168
15 2026-08-26 02:06 639233067787457832
33 ms 205.251.197.65
14 2026-08-26 01:49 639233057501801162
15 ms 52.11.168.168
13 2026-08-26 01:49 639233057501801162
15 ms 205.251.197.65
12 2026-08-26 01:32 639233047089431703
15 ms 205.251.197.65
11 2026-08-26 01:32 639233047089431703
15 ms 52.11.168.168
10 2026-08-26 01:14 639233036754790688
45 ms 205.251.197.65
9 2026-08-26 01:14 639233036754790688
45 ms 52.11.168.168
8 2026-08-26 00:57 639233026412602472
16 ms 205.251.197.65
7 2026-08-26 00:57 639233026412602472
16 ms 52.11.168.168
6 2026-08-26 00:40 639233016064066127
13 ms 52.11.168.168
5 2026-08-26 00:40 639233016064066127
13 ms 205.251.197.65
4 2026-08-26 00:23 639233005922655772
15 ms 52.11.168.168
3 2026-08-26 00:23 639233005922655772
15 ms 205.251.197.65
2 2026-08-26 00:06 639232995672256907
14 ms 205.251.197.65
1 2026-08-26 00:06 639232995672256907
14 ms 52.11.168.168