DNS response history for pike.netdoor.com

pike.netdoor.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 32 DNS check records, 32 successful responses, 0 failed responses, and 211 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 pike.netdoor.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

211 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.41.228.6

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 pike.netdoor.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
32 2026-08-25 11:27 639232535349285207
264 ms 206.41.228.6
31 2026-08-25 11:10 639232524938080723
136 ms 206.41.228.6
30 2026-08-25 10:16 639232492740373468
122 ms 206.41.228.6
29 2026-08-25 09:59 639232482235303141
303 ms 206.41.228.6
28 2026-08-25 09:41 639232471861770303
319 ms 206.41.228.6
27 2026-08-25 09:24 639232461630217327
319 ms 206.41.228.6
26 2026-08-25 09:07 639232451282965990
129 ms 206.41.228.6
25 2026-08-25 08:50 639232440814614938
295 ms 206.41.228.6
24 2026-08-25 08:32 639232430410720425
147 ms 206.41.228.6
23 2026-08-25 08:15 639232420003096185
153 ms 206.41.228.6
22 2026-08-25 07:58 639232409467287444
140 ms 206.41.228.6
21 2026-08-25 07:40 639232399077195997
258 ms 206.41.228.6
20 2026-08-25 07:23 639232388731528337
308 ms 206.41.228.6
19 2026-08-25 07:05 639232378288598612
267 ms 206.41.228.6
18 2026-08-25 06:12 639232346196373643
305 ms 206.41.228.6
17 2026-08-25 05:55 639232336112370741
574 ms 206.41.228.6
16 2026-08-25 05:38 639232326146508970
5 ms 206.41.228.6
15 2026-08-25 05:22 639232316189381720
142 ms 206.41.228.6
14 2026-08-25 05:05 639232306217998913
13 ms 206.41.228.6
13 2026-08-25 04:49 639232296255744174
134 ms 206.41.228.6
12 2026-08-25 04:32 639232286095760789
123 ms 206.41.228.6
11 2026-08-25 04:15 639232276086186273
133 ms 206.41.228.6
10 2026-08-25 03:58 639232265900986425
282 ms 206.41.228.6
9 2026-08-25 03:41 639232255723518075
144 ms 206.41.228.6
8 2026-08-25 03:24 639232245484452890
293 ms 206.41.228.6
7 2026-08-25 03:07 639232235157175331
252 ms 206.41.228.6
6 2026-08-25 02:14 639232203197189095
127 ms 206.41.228.6
5 2026-08-25 01:56 639232192844564298
270 ms 206.41.228.6
4 2026-08-25 01:39 639232182496008942
264 ms 206.41.228.6
3 2026-08-25 01:22 639232172197053132
257 ms 206.41.228.6
2 2026-08-25 00:29 639232140250307418
138 ms 206.41.228.6
1 2026-08-25 00:12 639232129927860324
138 ms 206.41.228.6