DNS response history for ns2.perdocere.org

ns2.perdocere.org 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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 550 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.perdocere.org.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

550 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

165.227.6.88

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.perdocere.org

Showing DNS history for 2026-08-25 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-25 12:05 639232556111768563
233 ms 165.227.6.88
33 2026-08-25 11:48 639232545839529039
226 ms 165.227.6.88
32 2026-08-25 11:31 639232535349285207
234 ms 165.227.6.88
31 2026-08-25 11:13 639232524938080723
231 ms 165.227.6.88
30 2026-08-25 10:19 639232492740373468
209 ms 165.227.6.88
29 2026-08-25 10:02 639232482235303141
219 ms 165.227.6.88
28 2026-08-25 09:45 639232471861770303
227 ms 165.227.6.88
27 2026-08-25 09:28 639232461630217327
2248 ms 165.227.6.88
26 2026-08-25 09:10 639232451282965990
213 ms 165.227.6.88
25 2026-08-25 08:53 639232440814614938
154 ms 165.227.6.88
24 2026-08-25 08:36 639232430410720425
226 ms 165.227.6.88
23 2026-08-25 08:18 639232420003096185
415 ms 165.227.6.88
22 2026-08-25 08:01 639232409467287444
2250 ms 165.227.6.88
21 2026-08-25 07:43 639232399077195997
218 ms 165.227.6.88
20 2026-08-25 07:26 639232388731528337
434 ms 165.227.6.88
19 2026-08-25 07:09 639232378288598612
2192 ms 165.227.6.88
18 2026-08-25 06:15 639232346196373643
107 ms 165.227.6.88
17 2026-08-25 05:58 639232336112370741
111 ms 165.227.6.88
16 2026-08-25 05:42 639232326146508970
218 ms 165.227.6.88
15 2026-08-25 05:25 639232316189381720
109 ms 165.227.6.88
14 2026-08-25 05:08 639232306217998913
117 ms 165.227.6.88
13 2026-08-25 04:52 639232296255744174
106 ms 165.227.6.88
12 2026-08-25 04:35 639232286095760789
309 ms 165.227.6.88
11 2026-08-25 04:18 639232276086186273
106 ms 165.227.6.88
10 2026-08-25 04:01 639232265900986425
107 ms 165.227.6.88
9 2026-08-25 03:44 639232255723518075
484 ms 165.227.6.88
8 2026-08-25 03:27 639232245484452890
222 ms 165.227.6.88
7 2026-08-25 03:10 639232235157175331
107 ms 165.227.6.88
6 2026-08-25 02:17 639232203197189095
3796 ms 165.227.6.88
5 2026-08-25 02:00 639232192844564298
228 ms 165.227.6.88
4 2026-08-25 01:43 639232182496008942
2234 ms 165.227.6.88
3 2026-08-25 01:25 639232172197053132
108 ms 165.227.6.88
2 2026-08-25 00:32 639232140250307418
191 ms 165.227.6.88
1 2026-08-25 00:15 639232129927860324
116 ms 165.227.6.88