DNS response history for ns2.sandiegocrimewatch.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.194.165.94

Most recently resolved hosting IP on selected date

Successful Responses

34

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.sandiegocrimewatch.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
34 2026-08-24 14:08 639231765923559455
169 ms 216.194.165.94
33 2026-08-24 13:51 639231755868832964
189 ms 216.194.165.94
32 2026-08-24 13:34 639231745628278877
338 ms 216.194.165.94
31 2026-08-24 13:17 639231735407682062
199 ms 216.194.165.94
30 2026-08-24 12:24 639231703815441688
314 ms 216.194.165.94
29 2026-08-24 12:08 639231693747052549
311 ms 216.194.165.94
28 2026-08-24 11:51 639231683712487276
274 ms 216.194.165.94
27 2026-08-24 11:34 639231673513573868
336 ms 216.194.165.94
26 2026-08-24 10:41 639231641791249939
323 ms 216.194.165.94
25 2026-08-24 10:24 639231631866211033
163 ms 216.194.165.94
24 2026-08-24 10:08 639231621644955316
324 ms 216.194.165.94
23 2026-08-24 09:51 639231611478799259
176 ms 216.194.165.94
22 2026-08-24 08:58 639231579923718211
319 ms 216.194.165.94
21 2026-08-24 08:41 639231569810702936
342 ms 216.194.165.94
20 2026-08-24 08:24 639231559762411619
312 ms 216.194.165.94
19 2026-08-24 08:07 639231549663595407
312 ms 216.194.165.94
18 2026-08-24 07:15 639231518076817246
314 ms 216.194.165.94
17 2026-08-24 06:58 639231508078650885
322 ms 216.194.165.94
16 2026-08-24 06:42 639231498210697093
308 ms 216.194.165.94
15 2026-08-24 06:25 639231488109699360
186 ms 216.194.165.94
14 2026-08-24 05:33 639231456772510692
315 ms 216.194.165.94
13 2026-08-24 05:16 639231447084631185
334 ms 216.194.165.94
12 2026-08-24 05:00 639231437208519473
329 ms 216.194.165.94
11 2026-08-24 04:43 639231427209627490
317 ms 216.194.165.94
10 2026-08-24 03:51 639231395791246644
328 ms 216.194.165.94
9 2026-08-24 03:35 639231386075551458
182 ms 216.194.165.94
8 2026-08-24 03:18 639231376208713791
311 ms 216.194.165.94
7 2026-08-24 03:02 639231366170589276
337 ms 216.194.165.94
6 2026-08-24 02:09 639231334732159368
313 ms 216.194.165.94
5 2026-08-24 01:53 639231325035670078
2253 ms 216.194.165.94
4 2026-08-24 01:37 639231315132253837
319 ms 216.194.165.94
3 2026-08-24 01:20 639231305014280808
187 ms 216.194.165.94
2 2026-08-24 00:27 639231273779380675
319 ms 216.194.165.94
1 2026-08-24 00:12 639231264180839154
314 ms 216.194.165.94