DNS response history for ns2.cox-sd.net

ns2.cox-sd.net 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 27 DNS check records, 27 successful responses, 0 failed responses, and 200 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.cox-sd.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

200 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.111.106.70

Most recently resolved hosting IP on selected date

Successful Responses

27

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.cox-sd.net

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
27 2026-08-30 08:43 639236755602384085
245 ms 68.111.106.70
26 2026-08-30 08:26 639236745600094925
134 ms 68.111.106.70
25 2026-08-30 08:09 639236735311262753
224 ms 68.111.106.70
24 2026-08-30 07:52 639236724996745235
9 ms 68.111.106.70
23 2026-08-30 07:35 639236714839899761
23 ms 68.111.106.70
22 2026-08-30 07:18 639236704748431488
252 ms 68.111.106.70
21 2026-08-30 07:01 639236694430128550
239 ms 68.111.106.70
20 2026-08-30 06:44 639236684143292417
342 ms 68.111.106.70
19 2026-08-30 06:27 639236673972499943
227 ms 68.111.106.70
18 2026-08-30 05:34 639236642126522802
345 ms 68.111.106.70
17 2026-08-30 05:17 639236632183518198
325 ms 68.111.106.70
16 2026-08-30 05:00 639236622289312589
8 ms 68.111.106.70
15 2026-08-30 04:44 639236612490676525
113 ms 68.111.106.70
14 2026-08-30 04:28 639236602582494852
224 ms 68.111.106.70
13 2026-08-30 04:11 639236592511706469
6 ms 68.111.106.70
12 2026-08-30 03:54 639236582441006869
226 ms 68.111.106.70
11 2026-08-30 03:38 639236572478785089
220 ms 68.111.106.70
10 2026-08-30 03:21 639236562556749999
267 ms 68.111.106.70
9 2026-08-30 03:04 639236552353482281
115 ms 68.111.106.70
8 2026-08-30 02:47 639236542188881607
227 ms 68.111.106.70
7 2026-08-30 02:30 639236531885440105
220 ms 68.111.106.70
6 2026-08-30 01:37 639236499922985383
553 ms 68.111.106.70
5 2026-08-30 01:20 639236489713594431
219 ms 68.111.106.70
4 2026-08-30 01:03 639236479750443901
114 ms 68.111.106.70
3 2026-08-30 00:46 639236469719936375
19 ms 68.111.106.70
2 2026-08-30 00:30 639236459579244885
283 ms 68.111.106.70
1 2026-08-30 00:13 639236449582837549
230 ms 68.111.106.70