DNS response history for ns2.cpeek.net

ns2.cpeek.net 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 35 DNS check records, 35 successful responses, 0 failed responses, and 252 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.cpeek.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

252 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.131.152.104

Most recently resolved hosting IP on selected date

Successful Responses

35

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.cpeek.net

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
35 2026-08-25 12:18 639232566381512620
2284 ms 208.131.152.104
34 2026-08-25 12:01 639232556111768563
285 ms 208.131.152.104
33 2026-08-25 11:44 639232545839529039
3 ms 208.131.152.104
32 2026-08-25 11:27 639232535349285207
282 ms 208.131.152.104
31 2026-08-25 11:09 639232524938080723
280 ms 208.131.152.104
30 2026-08-25 10:15 639232492740373468
5 ms 208.131.152.104
29 2026-08-25 09:58 639232482235303141
282 ms 208.131.152.104
28 2026-08-25 09:41 639232471861770303
3 ms 208.131.152.104
27 2026-08-25 09:23 639232461630217327
287 ms 208.131.152.104
26 2026-08-25 09:06 639232451282965990
8 ms 208.131.152.104
25 2026-08-25 08:49 639232440814614938
138 ms 208.131.152.104
24 2026-08-25 08:32 639232430410720425
4 ms 208.131.152.104
23 2026-08-25 08:14 639232420003096185
6 ms 208.131.152.104
22 2026-08-25 07:57 639232409467287444
287 ms 208.131.152.104
21 2026-08-25 07:39 639232399077195997
285 ms 208.131.152.104
20 2026-08-25 07:22 639232388731528337
281 ms 208.131.152.104
19 2026-08-25 07:05 639232378288598612
280 ms 208.131.152.104
18 2026-08-25 06:11 639232346196373643
283 ms 208.131.152.104
17 2026-08-25 05:54 639232336112370741
274 ms 208.131.152.104
16 2026-08-25 05:38 639232326146508970
143 ms 208.131.152.104
15 2026-08-25 05:21 639232316189381720
159 ms 208.131.152.104
14 2026-08-25 05:05 639232306217998913
285 ms 208.131.152.104
13 2026-08-25 04:48 639232296255744174
281 ms 208.131.152.104
12 2026-08-25 04:31 639232286095760789
143 ms 208.131.152.104
11 2026-08-25 04:14 639232276086186273
275 ms 208.131.152.104
10 2026-08-25 03:57 639232265900986425
279 ms 208.131.152.104
9 2026-08-25 03:40 639232255723518075
283 ms 208.131.152.104
8 2026-08-25 03:23 639232245484452890
283 ms 208.131.152.104
7 2026-08-25 03:06 639232235157175331
277 ms 208.131.152.104
6 2026-08-25 02:13 639232203197189095
283 ms 208.131.152.104
5 2026-08-25 01:56 639232192844564298
3 ms 208.131.152.104
4 2026-08-25 01:38 639232182496008942
4 ms 208.131.152.104
3 2026-08-25 01:21 639232172197053132
277 ms 208.131.152.104
2 2026-08-25 00:28 639232140250307418
3 ms 208.131.152.104
1 2026-08-25 00:11 639232129927860324
283 ms 208.131.152.104