DNS response history for ns1.netapike.com

ns1.netapike.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 28 DNS check records, 28 successful responses, 0 failed responses, and 588 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 ns1.netapike.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

588 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.21.208.232

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns1.netapike.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
28 2026-08-25 09:37 639232471861770303
68 ms 65.21.208.232
27 2026-08-25 09:20 639232461630217327
161 ms 65.21.208.232
26 2026-08-25 09:02 639232451282965990
128 ms 65.21.208.232
25 2026-08-25 08:45 639232440814614938
137 ms 65.21.208.232
24 2026-08-25 08:27 639232430410720425
60 ms 65.21.208.232
23 2026-08-25 08:10 639232420003096185
80 ms 65.21.208.232
22 2026-08-25 07:53 639232409467287444
2106 ms 65.21.208.232
21 2026-08-25 07:35 639232399077195997
55 ms 65.21.208.232
20 2026-08-25 07:18 639232388731528337
2013 ms 65.21.208.232
19 2026-08-25 07:01 639232378288598612
121 ms 65.21.208.232
18 2026-08-25 06:07 639232346196373643
129 ms 65.21.208.232
17 2026-08-25 05:50 639232336112370741
2016 ms 65.21.208.232
16 2026-08-25 05:34 639232326146508970
2093 ms 65.21.208.232
15 2026-08-25 05:17 639232316189381720
78 ms 65.21.208.232
14 2026-08-25 05:01 639232306217998913
71 ms 65.21.208.232
13 2026-08-25 04:44 639232296255744174
25 ms 65.21.208.232
12 2026-08-25 04:27 639232286095760789
136 ms 65.21.208.232
11 2026-08-25 04:10 639232276086186273
91 ms 65.21.208.232
10 2026-08-25 03:53 639232265900986425
129 ms 65.21.208.232
9 2026-08-25 03:36 639232255723518075
119 ms 65.21.208.232
8 2026-08-25 03:19 639232245484452890
2013 ms 65.21.208.232
7 2026-08-25 03:02 639232235157175331
2063 ms 65.21.208.232
6 2026-08-25 02:09 639232203197189095
117 ms 65.21.208.232
5 2026-08-25 01:52 639232192844564298
73 ms 65.21.208.232
4 2026-08-25 01:34 639232182496008942
2059 ms 65.21.208.232
3 2026-08-25 01:17 639232172197053132
129 ms 65.21.208.232
2 2026-08-25 00:24 639232140250307418
66 ms 65.21.208.232
1 2026-08-25 00:07 639232129927860324
122 ms 65.21.208.232