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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 180 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

28

Historical checks stored for this nameserver on selected date

Average Latency

180 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09: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

28

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-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
28 2026-08-25 09:43 639232471861770303
136 ms 68.111.106.70
27 2026-08-25 09:26 639232461630217327
111 ms 68.111.106.70
26 2026-08-25 09:09 639232451282965990
230 ms 68.111.106.70
25 2026-08-25 08:52 639232440814614938
228 ms 68.111.106.70
24 2026-08-25 08:34 639232430410720425
228 ms 68.111.106.70
23 2026-08-25 08:17 639232420003096185
127 ms 68.111.106.70
22 2026-08-25 08:00 639232409467287444
230 ms 68.111.106.70
21 2026-08-25 07:42 639232399077195997
6 ms 68.111.106.70
20 2026-08-25 07:25 639232388731528337
5 ms 68.111.106.70
19 2026-08-25 07:07 639232378288598612
223 ms 68.111.106.70
18 2026-08-25 06:14 639232346196373643
227 ms 68.111.106.70
17 2026-08-25 05:57 639232336112370741
223 ms 68.111.106.70
16 2026-08-25 05:40 639232326146508970
227 ms 68.111.106.70
15 2026-08-25 05:24 639232316189381720
183 ms 68.111.106.70
14 2026-08-25 05:07 639232306217998913
5 ms 68.111.106.70
13 2026-08-25 04:50 639232296255744174
230 ms 68.111.106.70
12 2026-08-25 04:34 639232286095760789
242 ms 68.111.106.70
11 2026-08-25 04:17 639232276086186273
240 ms 68.111.106.70
10 2026-08-25 04:00 639232265900986425
217 ms 68.111.106.70
9 2026-08-25 03:43 639232255723518075
4 ms 68.111.106.70
8 2026-08-25 03:26 639232245484452890
234 ms 68.111.106.70
7 2026-08-25 03:09 639232235157175331
286 ms 68.111.106.70
6 2026-08-25 02:16 639232203197189095
585 ms 68.111.106.70
5 2026-08-25 01:58 639232192844564298
219 ms 68.111.106.70
4 2026-08-25 01:41 639232182496008942
3 ms 68.111.106.70
3 2026-08-25 01:24 639232172197053132
117 ms 68.111.106.70
2 2026-08-25 00:30 639232140250307418
36 ms 68.111.106.70
1 2026-08-25 00:14 639232129927860324
243 ms 68.111.106.70