DNS response history for ns2.coppercare.com

ns2.coppercare.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 39 DNS check records, 39 successful responses, 0 failed responses, and 286 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.coppercare.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

286 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.68.191.139

Most recently resolved hosting IP on selected date

Successful Responses

39

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.coppercare.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
39 2026-08-25 13:31 639232608016476376
259 ms 64.68.191.139
38 2026-08-25 13:13 639232597643611557
8 ms 64.68.191.139
37 2026-08-25 12:56 639232587225721862
2128 ms 64.68.191.139
36 2026-08-25 12:39 639232576780683689
127 ms 64.68.191.139
35 2026-08-25 12:21 639232566381512620
261 ms 64.68.191.139
34 2026-08-25 12:04 639232556111768563
5 ms 64.68.191.139
33 2026-08-25 11:47 639232545839529039
262 ms 64.68.191.139
32 2026-08-25 11:30 639232535349285207
156 ms 64.68.191.139
31 2026-08-25 11:12 639232524938080723
253 ms 64.68.191.139
30 2026-08-25 10:18 639232492740373468
259 ms 64.68.191.139
29 2026-08-25 10:01 639232482235303141
126 ms 64.68.191.139
28 2026-08-25 09:44 639232471861770303
15 ms 64.68.191.139
27 2026-08-25 09:26 639232461630217327
16 ms 64.68.191.139
26 2026-08-25 09:09 639232451282965990
169 ms 64.68.191.139
25 2026-08-25 08:52 639232440814614938
130 ms 64.68.191.139
24 2026-08-25 08:35 639232430410720425
256 ms 64.68.191.139
23 2026-08-25 08:17 639232420003096185
2163 ms 64.68.191.139
22 2026-08-25 08:00 639232409467287444
260 ms 64.68.191.139
21 2026-08-25 07:42 639232399077195997
252 ms 64.68.191.139
20 2026-08-25 07:25 639232388731528337
174 ms 64.68.191.139
19 2026-08-25 07:08 639232378288598612
155 ms 64.68.191.139
18 2026-08-25 06:14 639232346196373643
130 ms 64.68.191.139
17 2026-08-25 05:57 639232336112370741
257 ms 64.68.191.139
16 2026-08-25 05:41 639232326146508970
268 ms 64.68.191.139
15 2026-08-25 05:24 639232316189381720
254 ms 64.68.191.139
14 2026-08-25 05:07 639232306217998913
253 ms 64.68.191.139
13 2026-08-25 04:51 639232296255744174
253 ms 64.68.191.139
12 2026-08-25 04:34 639232286095760789
265 ms 64.68.191.139
11 2026-08-25 04:17 639232276086186273
127 ms 64.68.191.139
10 2026-08-25 04:00 639232265900986425
6 ms 64.68.191.139
9 2026-08-25 03:43 639232255723518075
153 ms 64.68.191.139
8 2026-08-25 03:26 639232245484452890
256 ms 64.68.191.139
7 2026-08-25 03:09 639232235157175331
247 ms 64.68.191.139
6 2026-08-25 02:16 639232203197189095
252 ms 64.68.191.139
5 2026-08-25 01:59 639232192844564298
249 ms 64.68.191.139
4 2026-08-25 01:41 639232182496008942
249 ms 64.68.191.139
3 2026-08-25 01:24 639232172197053132
248 ms 64.68.191.139
2 2026-08-25 00:31 639232140250307418
134 ms 64.68.191.139
1 2026-08-25 00:14 639232129927860324
125 ms 64.68.191.139