DNS response history for ns2.wd1cks.org

ns2.wd1cks.org 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 33 DNS check records, 33 successful responses, 0 failed responses, and 720 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.wd1cks.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

720 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.60.157.176

Most recently resolved hosting IP on selected date

Successful Responses

33

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.wd1cks.org

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
33 2026-08-25 11:34 639232535349285207
832 ms 68.60.157.176
32 2026-08-25 11:16 639232524938080723
844 ms 68.60.157.176
31 2026-08-25 10:22 639232492740373468
452 ms 68.60.157.176
30 2026-08-25 10:05 639232482235303141
460 ms 68.60.157.176
29 2026-08-25 09:48 639232471861770303
649 ms 68.60.157.176
28 2026-08-25 09:30 639232461630217327
868 ms 68.60.157.176
27 2026-08-25 09:13 639232451282965990
945 ms 68.60.157.176
26 2026-08-25 08:56 639232440814614938
822 ms 68.60.157.176
25 2026-08-25 08:39 639232430410720425
477 ms 68.60.157.176
24 2026-08-25 08:21 639232420003096185
809 ms 68.60.157.176
23 2026-08-25 08:04 639232409467287444
478 ms 68.60.157.176
22 2026-08-25 07:46 639232399077195997
800 ms 68.60.157.176
21 2026-08-25 07:29 639232388731528337
815 ms 68.60.157.176
20 2026-08-25 07:12 639232378288598612
814 ms 68.60.157.176
19 2026-08-25 06:18 639232346196373643
457 ms 68.60.157.176
18 2026-08-25 06:01 639232336112370741
959 ms 68.60.157.176
17 2026-08-25 05:44 639232326146508970
819 ms 68.60.157.176
16 2026-08-25 05:28 639232316189381720
813 ms 68.60.157.176
15 2026-08-25 05:11 639232306217998913
481 ms 68.60.157.176
14 2026-08-25 04:55 639232296255744174
817 ms 68.60.157.176
13 2026-08-25 04:38 639232286095760789
467 ms 68.60.157.176
12 2026-08-25 04:21 639232276086186273
833 ms 68.60.157.176
11 2026-08-25 04:04 639232265900986425
825 ms 68.60.157.176
10 2026-08-25 03:47 639232255723518075
839 ms 68.60.157.176
9 2026-08-25 03:30 639232245484452890
815 ms 68.60.157.176
8 2026-08-25 03:13 639232235157175331
461 ms 68.60.157.176
7 2026-08-25 02:20 639232203197189095
467 ms 68.60.157.176
6 2026-08-25 02:03 639232192844564298
832 ms 68.60.157.176
5 2026-08-25 01:45 639232182496008942
820 ms 68.60.157.176
4 2026-08-25 01:28 639232172197053132
810 ms 68.60.157.176
3 2026-08-25 00:35 639232140250307418
835 ms 68.60.157.176
2 2026-08-25 00:18 639232129927860324
465 ms 68.60.157.176
1 2026-08-25 00:00 639232119551972438
867 ms 68.60.157.176