DNS response history for ns2.dcmpanel.com

ns2.dcmpanel.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 34 DNS check records, 33 successful responses, 1 failed responses, and 116 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.dcmpanel.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

116 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

178.239.115.6

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.dcmpanel.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
34 2026-08-25 11:58 639232556111768563
32 ms 178.239.115.6
33 2026-08-25 11:41 639232545839529039
221 ms 178.239.115.6
32 2026-08-25 11:23 639232535349285207
112 ms 178.239.115.6
31 2026-08-25 11:06 639232524938080723
107 ms 178.239.115.6
30 2026-08-25 10:12 639232492740373468
80 ms 178.239.115.6
29 2026-08-25 09:55 639232482235303141
79 ms 178.239.115.6
28 2026-08-25 09:37 639232471861770303
125 ms 178.239.115.6
27 2026-08-25 09:20 639232461630217327
149 ms 178.239.115.6
26 2026-08-25 09:03 639232451282965990
223 ms 178.239.115.6
25 2026-08-25 08:46 639232440814614938
97 ms 178.239.115.6
24 2026-08-25 08:28 639232430410720425
34 ms 178.239.115.6
23 2026-08-25 08:11 639232420003096185
113 ms 178.239.115.6
22 2026-08-25 07:53 639232409467287444
88 ms 178.239.115.6
21 2026-08-25 07:36 639232399077195997
70 ms 178.239.115.6
20 2026-08-25 07:19 639232388731528337
95 ms 178.239.115.6
19 2026-08-25 07:01 639232378288598612
62 ms 178.239.115.6
18 2026-08-25 06:08 639232346196373643
186 ms 178.239.115.6
17 2026-08-25 05:51 639232336112370741
136 ms 178.239.115.6
16 2026-08-25 05:34 639232326146508970
307 ms 178.239.115.6
15 2026-08-25 05:18 639232316189381720
67 ms 178.239.115.6
14 2026-08-25 05:01 639232306217998913
79 ms 178.239.115.6
13 2026-08-25 04:45 639232296255744174
118 ms 178.239.115.6
12 2026-08-25 04:28 639232286095760789
125 ms 178.239.115.6
11 2026-08-25 04:11 639232276086186273
91 ms 178.239.115.6
10 2026-08-25 03:54 639232265900986425
41 ms 178.239.115.6
9 2026-08-25 03:37 639232255723518075
123 ms 178.239.115.6
8 2026-08-25 03:20 639232245484452890
105 ms 178.239.115.6
7 2026-08-25 03:03 639232235157175331
97 ms 178.239.115.6
6 2026-08-25 02:09 639232203197189095
149 ms 178.239.115.6
5 2026-08-25 01:52 639232192844564298
107 ms 178.239.115.6
4 2026-08-25 01:35 639232182496008942
196 ms 178.239.115.6
3 2026-08-25 01:18 639232172197053132
-
2 2026-08-25 00:25 639232140250307418
100 ms 178.239.115.6
1 2026-08-25 00:07 639232129927860324
127 ms 178.239.115.6