DNS response history for ns1.ckm.co

ns1.ckm.co 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 36 DNS check records, 36 successful responses, 0 failed responses, and 398 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.ckm.co.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

398 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.50.120.107

Most recently resolved hosting IP on selected date

Successful Responses

36

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.ckm.co

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
36 2026-08-25 12:38 639232576780683689
240 ms 74.50.120.107
35 2026-08-25 12:20 639232566381512620
355 ms 74.50.120.107
34 2026-08-25 12:03 639232556111768563
146 ms 74.50.120.107
33 2026-08-25 11:46 639232545839529039
242 ms 74.50.120.107
32 2026-08-25 11:29 639232535349285207
392 ms 74.50.120.107
31 2026-08-25 11:11 639232524938080723
429 ms 74.50.120.107
30 2026-08-25 10:17 639232492740373468
399 ms 74.50.120.107
29 2026-08-25 10:00 639232482235303141
674 ms 74.50.120.107
28 2026-08-25 09:43 639232471861770303
156 ms 74.50.120.107
27 2026-08-25 09:25 639232461630217327
426 ms 74.50.120.107
26 2026-08-25 09:08 639232451282965990
392 ms 74.50.120.107
25 2026-08-25 08:51 639232440814614938
428 ms 74.50.120.107
24 2026-08-25 08:33 639232430410720425
416 ms 74.50.120.107
23 2026-08-25 08:16 639232420003096185
410 ms 74.50.120.107
22 2026-08-25 07:59 639232409467287444
367 ms 74.50.120.107
21 2026-08-25 07:41 639232399077195997
396 ms 74.50.120.107
20 2026-08-25 07:24 639232388731528337
151 ms 74.50.120.107
19 2026-08-25 07:07 639232378288598612
428 ms 74.50.120.107
18 2026-08-25 06:13 639232346196373643
409 ms 74.50.120.107
17 2026-08-25 05:56 639232336112370741
403 ms 74.50.120.107
16 2026-08-25 05:40 639232326146508970
2 ms 74.50.120.107
15 2026-08-25 05:23 639232316189381720
2032 ms 74.50.120.107
14 2026-08-25 05:06 639232306217998913
422 ms 74.50.120.107
13 2026-08-25 04:50 639232296255744174
242 ms 74.50.120.107
12 2026-08-25 04:33 639232286095760789
230 ms 74.50.120.107
11 2026-08-25 04:16 639232276086186273
244 ms 74.50.120.107
10 2026-08-25 03:59 639232265900986425
233 ms 74.50.120.107
9 2026-08-25 03:42 639232255723518075
168 ms 74.50.120.107
8 2026-08-25 03:25 639232245484452890
230 ms 74.50.120.107
7 2026-08-25 03:08 639232235157175331
236 ms 74.50.120.107
6 2026-08-25 02:15 639232203197189095
158 ms 74.50.120.107
5 2026-08-25 01:58 639232192844564298
230 ms 74.50.120.107
4 2026-08-25 01:40 639232182496008942
9 ms 74.50.120.107
3 2026-08-25 01:23 639232172197053132
235 ms 74.50.120.107
2 2026-08-25 00:30 639232140250307418
279 ms 74.50.120.107
1 2026-08-25 00:13 639232129927860324
2116 ms 74.50.120.107