DNS response history for ns3.cpuworx.com

ns3.cpuworx.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-30. For this date, NameServerHistory found 38 DNS check records, 36 successful responses, 2 failed responses, and 314 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 ns3.cpuworx.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.210.106.38

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns3.cpuworx.com

Showing DNS history for 2026-08-30 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
38 2026-08-30 12:11 639236878057367680
-
37 2026-08-30 11:55 639236867916029489
7 ms 206.210.106.38
36 2026-08-30 11:38 639236858088772005
109 ms 206.210.106.38
35 2026-08-30 11:21 639236848158742395
222 ms 206.210.106.38
34 2026-08-30 11:05 639236838137395574
220 ms 206.210.106.38
33 2026-08-30 10:48 639236827967386881
678 ms 206.210.106.38
32 2026-08-30 10:31 639236817708615077
228 ms 206.210.106.38
31 2026-08-30 09:38 639236785770651804
108 ms 206.210.106.38
30 2026-08-30 09:21 639236775820686373
3 ms 206.210.106.38
29 2026-08-30 09:04 639236765768339082
221 ms 206.210.106.38
28 2026-08-30 08:47 639236755602384085
222 ms 206.210.106.38
27 2026-08-30 08:30 639236745600094925
222 ms 206.210.106.38
26 2026-08-30 08:14 639236735311262753
-
25 2026-08-30 07:57 639236724996745235
218 ms 206.210.106.38
24 2026-08-30 07:39 639236714839899761
559 ms 206.210.106.38
23 2026-08-30 07:23 639236704748431488
2 ms 206.210.106.38
22 2026-08-30 07:06 639236694430128550
575 ms 206.210.106.38
21 2026-08-30 06:48 639236684143292417
232 ms 206.210.106.38
20 2026-08-30 06:31 639236673972499943
220 ms 206.210.106.38
19 2026-08-30 05:38 639236642126522802
2 ms 206.210.106.38
18 2026-08-30 05:21 639236632183518198
233 ms 206.210.106.38
17 2026-08-30 05:05 639236622289312589
442 ms 206.210.106.38
16 2026-08-30 04:48 639236612490676525
220 ms 206.210.106.38
15 2026-08-30 04:32 639236602582494852
2 ms 206.210.106.38
14 2026-08-30 04:16 639236592511706469
220 ms 206.210.106.38
13 2026-08-30 03:59 639236582441006869
2 ms 206.210.106.38
12 2026-08-30 03:42 639236572478785089
2 ms 206.210.106.38
11 2026-08-30 03:25 639236562556749999
219 ms 206.210.106.38
10 2026-08-30 03:09 639236552353482281
1117 ms 206.210.106.38
9 2026-08-30 02:52 639236542188881607
222 ms 206.210.106.38
8 2026-08-30 02:35 639236531885440105
456 ms 206.210.106.38
7 2026-08-30 01:41 639236499922985383
108 ms 206.210.106.38
6 2026-08-30 01:24 639236489713594431
2 ms 206.210.106.38
5 2026-08-30 01:07 639236479750443901
2990 ms 206.210.106.38
4 2026-08-30 00:51 639236469719936375
585 ms 206.210.106.38
3 2026-08-30 00:34 639236459579244885
224 ms 206.210.106.38
2 2026-08-30 00:17 639236449582837549
223 ms 206.210.106.38
1 2026-08-30 00:00 639236439461653110
3 ms 206.210.106.38