DNS response history for ns2.wcode.club

ns2.wcode.club 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 437 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.wcode.club.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

437 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

175.110.115.237

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 ns2.wcode.club

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:33 639232576780683689
20 ms 175.110.115.237
35 2026-08-25 12:16 639232566381512620
20 ms 175.110.115.237
34 2026-08-25 11:58 639232556111768563
9 ms 175.110.115.237
33 2026-08-25 11:41 639232545839529039
75 ms 175.110.115.237
32 2026-08-25 11:24 639232535349285207
94 ms 175.110.115.237
31 2026-08-25 11:06 639232524938080723
2053 ms 175.110.115.237
30 2026-08-25 10:13 639232492740373468
72 ms 175.110.115.237
29 2026-08-25 09:55 639232482235303141
26 ms 175.110.115.237
28 2026-08-25 09:38 639232471861770303
39 ms 175.110.115.237
27 2026-08-25 09:21 639232461630217327
50 ms 175.110.115.237
26 2026-08-25 09:04 639232451282965990
2097 ms 175.110.115.237
25 2026-08-25 08:46 639232440814614938
1598 ms 175.110.115.237
24 2026-08-25 08:29 639232430410720425
51 ms 175.110.115.237
23 2026-08-25 08:12 639232420003096185
47 ms 175.110.115.237
22 2026-08-25 07:54 639232409467287444
2022 ms 175.110.115.237
21 2026-08-25 07:37 639232399077195997
90 ms 175.110.115.237
20 2026-08-25 07:19 639232388731528337
2153 ms 175.110.115.237
19 2026-08-25 07:02 639232378288598612
43 ms 175.110.115.237
18 2026-08-25 06:08 639232346196373643
51 ms 175.110.115.237
17 2026-08-25 05:52 639232336112370741
60 ms 175.110.115.237
16 2026-08-25 05:35 639232326146508970
125 ms 175.110.115.237
15 2026-08-25 05:18 639232316189381720
74 ms 175.110.115.237
14 2026-08-25 05:02 639232306217998913
9 ms 175.110.115.237
13 2026-08-25 04:45 639232296255744174
39 ms 175.110.115.237
12 2026-08-25 04:28 639232286095760789
36 ms 175.110.115.237
11 2026-08-25 04:12 639232276086186273
98 ms 175.110.115.237
10 2026-08-25 03:55 639232265900986425
72 ms 175.110.115.237
9 2026-08-25 03:38 639232255723518075
62 ms 175.110.115.237
8 2026-08-25 03:21 639232245484452890
43 ms 175.110.115.237
7 2026-08-25 03:03 639232235157175331
149 ms 175.110.115.237
6 2026-08-25 02:10 639232203197189095
2039 ms 175.110.115.237
5 2026-08-25 01:53 639232192844564298
2073 ms 175.110.115.237
4 2026-08-25 01:36 639232182496008942
44 ms 175.110.115.237
3 2026-08-25 01:18 639232172197053132
72 ms 175.110.115.237
2 2026-08-25 00:25 639232140250307418
82 ms 175.110.115.237
1 2026-08-25 00:08 639232129927860324
45 ms 175.110.115.237