DNS response history for ns1.minneapoliscrimewatch.com

ns1.minneapoliscrimewatch.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 33 DNS check records, 33 successful responses, 0 failed responses, and 289 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 ns1.minneapoliscrimewatch.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

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

33

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 ns1.minneapoliscrimewatch.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
33 2026-08-25 11:49 639232545839529039
321 ms 216.194.165.94
32 2026-08-25 11:31 639232535349285207
337 ms 216.194.165.94
31 2026-08-25 11:14 639232524938080723
164 ms 216.194.165.94
30 2026-08-25 10:20 639232492740373468
318 ms 216.194.165.94
29 2026-08-25 10:03 639232482235303141
171 ms 216.194.165.94
28 2026-08-25 09:45 639232471861770303
318 ms 216.194.165.94
27 2026-08-25 09:28 639232461630217327
163 ms 216.194.165.94
26 2026-08-25 09:11 639232451282965990
329 ms 216.194.165.94
25 2026-08-25 08:54 639232440814614938
322 ms 216.194.165.94
24 2026-08-25 08:36 639232430410720425
323 ms 216.194.165.94
23 2026-08-25 08:19 639232420003096185
324 ms 216.194.165.94
22 2026-08-25 08:02 639232409467287444
322 ms 216.194.165.94
21 2026-08-25 07:44 639232399077195997
313 ms 216.194.165.94
20 2026-08-25 07:27 639232388731528337
323 ms 216.194.165.94
19 2026-08-25 07:09 639232378288598612
335 ms 216.194.165.94
18 2026-08-25 06:16 639232346196373643
319 ms 216.194.165.94
17 2026-08-25 05:59 639232336112370741
322 ms 216.194.165.94
16 2026-08-25 05:42 639232326146508970
320 ms 216.194.165.94
15 2026-08-25 05:26 639232316189381720
267 ms 216.194.165.94
14 2026-08-25 05:09 639232306217998913
177 ms 216.194.165.94
13 2026-08-25 04:52 639232296255744174
172 ms 216.194.165.94
12 2026-08-25 04:36 639232286095760789
169 ms 216.194.165.94
11 2026-08-25 04:19 639232276086186273
348 ms 216.194.165.94
10 2026-08-25 04:02 639232265900986425
323 ms 216.194.165.94
9 2026-08-25 03:45 639232255723518075
317 ms 216.194.165.94
8 2026-08-25 03:28 639232245484452890
316 ms 216.194.165.94
7 2026-08-25 03:11 639232235157175331
322 ms 216.194.165.94
6 2026-08-25 02:18 639232203197189095
341 ms 216.194.165.94
5 2026-08-25 02:01 639232192844564298
315 ms 216.194.165.94
4 2026-08-25 01:43 639232182496008942
329 ms 216.194.165.94
3 2026-08-25 01:26 639232172197053132
158 ms 216.194.165.94
2 2026-08-25 00:33 639232140250307418
330 ms 216.194.165.94
1 2026-08-25 00:16 639232129927860324
325 ms 216.194.165.94