DNS response history for hogplesk.prolink.de

hogplesk.prolink.de 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-27. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 242 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 hogplesk.prolink.de.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

88.99.85.166

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 hogplesk.prolink.de

Showing DNS history for 2026-08-27 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-27 09:02 639234181105879568
23 ms 88.99.85.166
27 2026-08-27 08:44 639234170713214496
59 ms 88.99.85.166
26 2026-08-27 08:27 639234160341037652
24 ms 88.99.85.166
25 2026-08-27 08:09 639234149799404224
21 ms 88.99.85.166
24 2026-08-27 07:52 639234139553286469
26 ms 88.99.85.166
23 2026-08-27 06:58 639234107183588293
36 ms 88.99.85.166
22 2026-08-27 06:41 639234096905435724
2019 ms 88.99.85.166
21 2026-08-27 06:24 639234086579410775
24 ms 88.99.85.166
20 2026-08-27 06:07 639234076291157956
18 ms 88.99.85.166
19 2026-08-27 05:50 639234065981939454
12 ms 88.99.85.166
18 2026-08-27 05:32 639234055548642997
41 ms 88.99.85.166
17 2026-08-27 05:15 639234045267979603
17 ms 88.99.85.166
16 2026-08-27 04:58 639234034999717463
12 ms 88.99.85.166
15 2026-08-27 04:41 639234024739225358
28 ms 88.99.85.166
14 2026-08-27 04:24 639234014311170162
12 ms 88.99.85.166
13 2026-08-27 04:06 639234003806017640
40 ms 88.99.85.166
12 2026-08-27 03:49 639233993356203030
30 ms 88.99.85.166
11 2026-08-27 02:55 639233961301716608
13 ms 88.99.85.166
10 2026-08-27 02:38 639233950834200647
66 ms 88.99.85.166
9 2026-08-27 02:20 639233940431849026
20 ms 88.99.85.166
8 2026-08-27 02:03 639233930110596398
37 ms 88.99.85.166
7 2026-08-27 01:46 639233919705434540
29 ms 88.99.85.166
6 2026-08-27 01:29 639233909452807845
2020 ms 88.99.85.166
5 2026-08-27 01:12 639233899096420820
32 ms 88.99.85.166
4 2026-08-27 00:54 639233888707824939
2017 ms 88.99.85.166
3 2026-08-27 00:37 639233878461203802
25 ms 88.99.85.166
2 2026-08-27 00:20 639233868060868209
39 ms 88.99.85.166
1 2026-08-27 00:02 639233857450922991
23 ms 88.99.85.166