DNS response history for ns2.poliagendo.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

166 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.241.107.12

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.poliagendo.com

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:04 639232556111768563
276 ms 162.241.107.12
33 2026-08-25 11:47 639232545839529039
164 ms 162.241.107.12
32 2026-08-25 11:29 639232535349285207
275 ms 162.241.107.12
31 2026-08-25 11:12 639232524938080723
4 ms 162.241.107.12
30 2026-08-25 10:18 639232492740373468
138 ms 162.241.107.12
29 2026-08-25 10:01 639232482235303141
276 ms 162.241.107.12
28 2026-08-25 09:43 639232471861770303
275 ms 162.241.107.12
27 2026-08-25 09:26 639232461630217327
280 ms 162.241.107.12
26 2026-08-25 09:09 639232451282965990
281 ms 162.241.107.12
25 2026-08-25 08:52 639232440814614938
297 ms 162.241.107.12
24 2026-08-25 08:34 639232430410720425
187 ms 162.241.107.12
23 2026-08-25 08:17 639232420003096185
276 ms 162.241.107.12
22 2026-08-25 08:00 639232409467287444
274 ms 162.241.107.12
21 2026-08-25 07:42 639232399077195997
293 ms 162.241.107.12
20 2026-08-25 07:25 639232388731528337
160 ms 162.241.107.12
19 2026-08-25 07:07 639232378288598612
273 ms 162.241.107.12
18 2026-08-25 06:14 639232346196373643
22 ms 162.241.107.12
17 2026-08-25 05:57 639232336112370741
10 ms 162.241.107.12
16 2026-08-25 05:40 639232326146508970
10 ms 162.241.107.12
15 2026-08-25 05:24 639232316189381720
7 ms 162.241.107.12
14 2026-08-25 05:07 639232306217998913
286 ms 162.241.107.12
13 2026-08-25 04:50 639232296255744174
285 ms 162.241.107.12
12 2026-08-25 04:34 639232286095760789
139 ms 162.241.107.12
11 2026-08-25 04:17 639232276086186273
138 ms 162.241.107.12
10 2026-08-25 04:00 639232265900986425
144 ms 162.241.107.12
9 2026-08-25 03:43 639232255723518075
4 ms 162.241.107.12
8 2026-08-25 03:26 639232245484452890
136 ms 162.241.107.12
7 2026-08-25 03:09 639232235157175331
4 ms 162.241.107.12
6 2026-08-25 02:16 639232203197189095
6 ms 162.241.107.12
5 2026-08-25 01:58 639232192844564298
23 ms 162.241.107.12
4 2026-08-25 01:41 639232182496008942
142 ms 162.241.107.12
3 2026-08-25 01:24 639232172197053132
276 ms 162.241.107.12
2 2026-08-25 00:30 639232140250307418
4 ms 162.241.107.12
1 2026-08-25 00:14 639232129927860324
276 ms 162.241.107.12