DNS response history for ns2.perdocere.net

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

32

Historical checks stored for this nameserver on selected date

Average Latency

258 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:28

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

32

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.net

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
32 2026-08-25 11:28 639232535349285207
424 ms 165.227.6.88
31 2026-08-25 11:11 639232524938080723
222 ms 165.227.6.88
30 2026-08-25 10:17 639232492740373468
222 ms 165.227.6.88
29 2026-08-25 10:00 639232482235303141
252 ms 165.227.6.88
28 2026-08-25 09:42 639232471861770303
229 ms 165.227.6.88
27 2026-08-25 09:25 639232461630217327
220 ms 165.227.6.88
26 2026-08-25 09:08 639232451282965990
228 ms 165.227.6.88
25 2026-08-25 08:51 639232440814614938
280 ms 165.227.6.88
24 2026-08-25 08:33 639232430410720425
235 ms 165.227.6.88
23 2026-08-25 08:16 639232420003096185
230 ms 165.227.6.88
22 2026-08-25 07:59 639232409467287444
236 ms 165.227.6.88
21 2026-08-25 07:41 639232399077195997
228 ms 165.227.6.88
20 2026-08-25 07:24 639232388731528337
224 ms 165.227.6.88
19 2026-08-25 07:06 639232378288598612
283 ms 165.227.6.88
18 2026-08-25 06:13 639232346196373643
246 ms 165.227.6.88
17 2026-08-25 05:56 639232336112370741
314 ms 165.227.6.88
16 2026-08-25 05:39 639232326146508970
248 ms 165.227.6.88
15 2026-08-25 05:23 639232316189381720
265 ms 165.227.6.88
14 2026-08-25 05:06 639232306217998913
357 ms 165.227.6.88
13 2026-08-25 04:50 639232296255744174
224 ms 165.227.6.88
12 2026-08-25 04:33 639232286095760789
235 ms 165.227.6.88
11 2026-08-25 04:16 639232276086186273
222 ms 165.227.6.88
10 2026-08-25 03:59 639232265900986425
214 ms 165.227.6.88
9 2026-08-25 03:42 639232255723518075
239 ms 165.227.6.88
8 2026-08-25 03:25 639232245484452890
222 ms 165.227.6.88
7 2026-08-25 03:08 639232235157175331
579 ms 165.227.6.88
6 2026-08-25 02:15 639232203197189095
168 ms 165.227.6.88
5 2026-08-25 01:57 639232192844564298
313 ms 165.227.6.88
4 2026-08-25 01:40 639232182496008942
219 ms 165.227.6.88
3 2026-08-25 01:23 639232172197053132
240 ms 165.227.6.88
2 2026-08-25 00:30 639232140250307418
233 ms 165.227.6.88
1 2026-08-25 00:13 639232129927860324
220 ms 165.227.6.88