DNS response history for ns1.neocopper.com

ns1.neocopper.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 372 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.neocopper.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

372 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.130.229

Most recently resolved hosting IP on selected date

Successful Responses

26

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.neocopper.com

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:42 639231641791249939
290 ms 162.214.130.229
25 2026-08-24 10:26 639231631866211033
293 ms 162.214.130.229
24 2026-08-24 10:09 639231621644955316
291 ms 162.214.130.229
23 2026-08-24 09:52 639231611478799259
2156 ms 162.214.130.229
22 2026-08-24 08:59 639231579923718211
292 ms 162.214.130.229
21 2026-08-24 08:43 639231569810702936
317 ms 162.214.130.229
20 2026-08-24 08:26 639231559762411619
3657 ms 162.214.130.229
19 2026-08-24 08:09 639231549663595407
282 ms 162.214.130.229
18 2026-08-24 07:16 639231518076817246
146 ms 162.214.130.229
17 2026-08-24 07:00 639231508078650885
254 ms 162.214.130.229
16 2026-08-24 06:43 639231498210697093
295 ms 162.214.130.229
15 2026-08-24 06:26 639231488109699360
292 ms 162.214.130.229
14 2026-08-24 05:34 639231456772510692
3 ms 162.214.130.229
13 2026-08-24 05:18 639231447084631185
3 ms 162.214.130.229
12 2026-08-24 05:01 639231437208519473
4 ms 162.214.130.229
11 2026-08-24 04:45 639231427209627490
3 ms 162.214.130.229
10 2026-08-24 03:52 639231395791246644
299 ms 162.214.130.229
9 2026-08-24 03:36 639231386075551458
175 ms 162.214.130.229
8 2026-08-24 03:20 639231376208713791
295 ms 162.214.130.229
7 2026-08-24 03:03 639231366170589276
145 ms 162.214.130.229
6 2026-08-24 02:11 639231334732159368
3 ms 162.214.130.229
5 2026-08-24 01:54 639231325035670078
3 ms 162.214.130.229
4 2026-08-24 01:38 639231315132253837
15 ms 162.214.130.229
3 2026-08-24 01:21 639231305014280808
143 ms 162.214.130.229
2 2026-08-24 00:29 639231273779380675
3 ms 162.214.130.229
1 2026-08-24 00:13 639231264180839154
3 ms 162.214.130.229