DNS response history for ns2.washingtoncrimewatch.com

ns2.washingtoncrimewatch.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-25. For this date, NameServerHistory found 18 DNS check records, 18 successful responses, 0 failed responses, and 264 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.washingtoncrimewatch.com.
Records on Selected Date

18

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:15

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

18

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

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
18 2026-08-25 06:15 639232346196373643
315 ms 216.194.165.94
17 2026-08-25 05:58 639232336112370741
169 ms 216.194.165.94
16 2026-08-25 05:41 639232326146508970
165 ms 216.194.165.94
15 2026-08-25 05:24 639232316189381720
327 ms 216.194.165.94
14 2026-08-25 05:08 639232306217998913
230 ms 216.194.165.94
13 2026-08-25 04:51 639232296255744174
154 ms 216.194.165.94
12 2026-08-25 04:34 639232286095760789
321 ms 216.194.165.94
11 2026-08-25 04:17 639232276086186273
205 ms 216.194.165.94
10 2026-08-25 04:01 639232265900986425
321 ms 216.194.165.94
9 2026-08-25 03:44 639232255723518075
318 ms 216.194.165.94
8 2026-08-25 03:27 639232245484452890
163 ms 216.194.165.94
7 2026-08-25 03:10 639232235157175331
319 ms 216.194.165.94
6 2026-08-25 02:16 639232203197189095
329 ms 216.194.165.94
5 2026-08-25 01:59 639232192844564298
315 ms 216.194.165.94
4 2026-08-25 01:42 639232182496008942
318 ms 216.194.165.94
3 2026-08-25 01:25 639232172197053132
316 ms 216.194.165.94
2 2026-08-25 00:31 639232140250307418
159 ms 216.194.165.94
1 2026-08-25 00:14 639232129927860324
313 ms 216.194.165.94