DNS response history for ns2.coropolipty.org

ns2.coropolipty.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 31 DNS check records, 31 successful responses, 0 failed responses, and 265 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.coropolipty.org.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

265 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.220.53.118

Most recently resolved hosting IP on selected date

Successful Responses

31

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.coropolipty.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
31 2026-08-25 11:11 639232524938080723
322 ms 31.220.53.118
30 2026-08-25 10:17 639232492740373468
190 ms 31.220.53.118
29 2026-08-25 10:00 639232482235303141
157 ms 31.220.53.118
28 2026-08-25 09:42 639232471861770303
444 ms 31.220.53.118
27 2026-08-25 09:25 639232461630217327
158 ms 31.220.53.118
26 2026-08-25 09:08 639232451282965990
337 ms 31.220.53.118
25 2026-08-25 08:51 639232440814614938
439 ms 31.220.53.118
24 2026-08-25 08:33 639232430410720425
156 ms 31.220.53.118
23 2026-08-25 08:16 639232420003096185
317 ms 31.220.53.118
22 2026-08-25 07:58 639232409467287444
326 ms 31.220.53.118
21 2026-08-25 07:41 639232399077195997
163 ms 31.220.53.118
20 2026-08-25 07:24 639232388731528337
315 ms 31.220.53.118
19 2026-08-25 07:06 639232378288598612
324 ms 31.220.53.118
18 2026-08-25 06:13 639232346196373643
2 ms 31.220.53.118
17 2026-08-25 05:56 639232336112370741
4 ms 31.220.53.118
16 2026-08-25 05:39 639232326146508970
7 ms 31.220.53.118
15 2026-08-25 05:23 639232316189381720
164 ms 31.220.53.118
14 2026-08-25 05:06 639232306217998913
331 ms 31.220.53.118
13 2026-08-25 04:49 639232296255744174
4 ms 31.220.53.118
12 2026-08-25 04:33 639232286095760789
173 ms 31.220.53.118
11 2026-08-25 04:16 639232276086186273
316 ms 31.220.53.118
10 2026-08-25 03:59 639232265900986425
322 ms 31.220.53.118
9 2026-08-25 03:42 639232255723518075
335 ms 31.220.53.118
8 2026-08-25 03:25 639232245484452890
543 ms 31.220.53.118
7 2026-08-25 03:08 639232235157175331
327 ms 31.220.53.118
6 2026-08-25 02:14 639232203197189095
321 ms 31.220.53.118
5 2026-08-25 01:57 639232192844564298
317 ms 31.220.53.118
4 2026-08-25 01:40 639232182496008942
433 ms 31.220.53.118
3 2026-08-25 01:23 639232172197053132
551 ms 31.220.53.118
2 2026-08-25 00:29 639232140250307418
170 ms 31.220.53.118
1 2026-08-25 00:12 639232129927860324
239 ms 31.220.53.118