DNS response history for ns2.apark.online

ns2.apark.online 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 29 DNS check records, 29 successful responses, 0 failed responses, and 329 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.apark.online.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

329 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.0.217.132

Most recently resolved hosting IP on selected date

Successful Responses

29

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.apark.online

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
29 2026-08-25 09:54 639232482235303141
34 ms 162.0.217.132
28 2026-08-25 09:36 639232471861770303
50 ms 162.0.217.132
27 2026-08-25 09:19 639232461630217327
2180 ms 162.0.217.132
26 2026-08-25 09:02 639232451282965990
96 ms 162.0.217.132
25 2026-08-25 08:45 639232440814614938
2092 ms 162.0.217.132
24 2026-08-25 08:27 639232430410720425
2183 ms 162.0.217.132
23 2026-08-25 08:10 639232420003096185
14 ms 162.0.217.132
22 2026-08-25 07:52 639232409467287444
33 ms 162.0.217.132
21 2026-08-25 07:35 639232399077195997
45 ms 162.0.217.132
20 2026-08-25 07:18 639232388731528337
2028 ms 162.0.217.132
19 2026-08-25 07:01 639232378288598612
46 ms 162.0.217.132
18 2026-08-25 06:07 639232346196373643
8 ms 162.0.217.132
17 2026-08-25 05:50 639232336112370741
58 ms 162.0.217.132
16 2026-08-25 05:33 639232326146508970
60 ms 162.0.217.132
15 2026-08-25 05:17 639232316189381720
50 ms 162.0.217.132
14 2026-08-25 05:00 639232306217998913
29 ms 162.0.217.132
13 2026-08-25 04:44 639232296255744174
121 ms 162.0.217.132
12 2026-08-25 04:27 639232286095760789
46 ms 162.0.217.132
11 2026-08-25 04:10 639232276086186273
27 ms 162.0.217.132
10 2026-08-25 03:53 639232265900986425
46 ms 162.0.217.132
9 2026-08-25 03:36 639232255723518075
7 ms 162.0.217.132
8 2026-08-25 03:19 639232245484452890
22 ms 162.0.217.132
7 2026-08-25 03:02 639232235157175331
48 ms 162.0.217.132
6 2026-08-25 02:09 639232203197189095
19 ms 162.0.217.132
5 2026-08-25 01:51 639232192844564298
17 ms 162.0.217.132
4 2026-08-25 01:34 639232182496008942
80 ms 162.0.217.132
3 2026-08-25 01:17 639232172197053132
19 ms 162.0.217.132
2 2026-08-25 00:24 639232140250307418
56 ms 162.0.217.132
1 2026-08-25 00:06 639232129927860324
32 ms 162.0.217.132