DNS response history for 36ns.plenacom.com

36ns.plenacom.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 21 DNS check records, 20 successful responses, 1 failed responses, and 123 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 36ns.plenacom.com.
Records on Selected Date

21

Historical checks stored for this nameserver on selected date

Average Latency

123 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 08:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.35.105.202

Most recently resolved hosting IP on selected date

Successful Responses

20

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for 36ns.plenacom.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
21 2026-08-24 08:29 639231569810702936
15 ms 37.35.105.202
20 2026-08-24 08:13 639231559762411619
21 ms 37.35.105.202
19 2026-08-24 07:56 639231549663595407
17 ms 37.35.105.202
18 2026-08-24 07:03 639231518076817246
9 ms 37.35.105.202
17 2026-08-24 06:46 639231508078650885
65 ms 37.35.105.202
16 2026-08-24 06:30 639231498210697093
16 ms 37.35.105.202
15 2026-08-24 06:13 639231488109699360
67 ms 37.35.105.202
14 2026-08-24 05:21 639231456772510692
12 ms 37.35.105.202
13 2026-08-24 05:05 639231447084631185
2033 ms 37.35.105.202
12 2026-08-24 04:48 639231437208519473
3 ms 37.35.105.202
11 2026-08-24 04:32 639231427209627490
15 ms 37.35.105.202
10 2026-08-24 03:39 639231395791246644
24 ms 37.35.105.202
9 2026-08-24 03:23 639231386075551458
3 ms 37.35.105.202
8 2026-08-24 03:07 639231376208713791
38 ms 37.35.105.202
7 2026-08-24 02:50 639231366170589276
30 ms 37.35.105.202
6 2026-08-24 01:58 639231334732159368
5 ms 37.35.105.202
5 2026-08-24 01:41 639231325035670078
14 ms 37.35.105.202
4 2026-08-24 01:25 639231315132253837
27 ms 37.35.105.202
3 2026-08-24 01:08 639231305014280808
30 ms 37.35.105.202
2 2026-08-24 00:16 639231273779380675
-
1 2026-08-24 00:00 639231264180839154
24 ms 37.35.105.202