DNS response history for ns2.crcom.net

ns2.crcom.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 415 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.crcom.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

415 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.55.192.102

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.crcom.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:41 639232471861770303
2007 ms 69.55.192.102
27 2026-08-25 09:24 639232461630217327
278 ms 69.55.192.102
26 2026-08-25 09:07 639232451282965990
125 ms 69.55.192.102
25 2026-08-25 08:49 639232440814614938
279 ms 69.55.192.102
24 2026-08-25 08:32 639232430410720425
235 ms 69.55.192.102
23 2026-08-25 08:15 639232420003096185
239 ms 69.55.192.102
22 2026-08-25 07:57 639232409467287444
244 ms 69.55.192.102
21 2026-08-25 07:40 639232399077195997
243 ms 69.55.192.102
20 2026-08-25 07:23 639232388731528337
2019 ms 69.55.192.102
19 2026-08-25 07:05 639232378288598612
135 ms 69.55.192.102
18 2026-08-25 06:12 639232346196373643
246 ms 69.55.192.102
17 2026-08-25 05:55 639232336112370741
270 ms 69.55.192.102
16 2026-08-25 05:38 639232326146508970
4 ms 69.55.192.102
15 2026-08-25 05:22 639232316189381720
24 ms 69.55.192.102
14 2026-08-25 05:05 639232306217998913
234 ms 69.55.192.102
13 2026-08-25 04:48 639232296255744174
259 ms 69.55.192.102
12 2026-08-25 04:32 639232286095760789
255 ms 69.55.192.102
11 2026-08-25 04:15 639232276086186273
265 ms 69.55.192.102
10 2026-08-25 03:58 639232265900986425
244 ms 69.55.192.102
9 2026-08-25 03:41 639232255723518075
267 ms 69.55.192.102
8 2026-08-25 03:24 639232245484452890
243 ms 69.55.192.102
7 2026-08-25 03:07 639232235157175331
280 ms 69.55.192.102
6 2026-08-25 02:13 639232203197189095
180 ms 69.55.192.102
5 2026-08-25 01:56 639232192844564298
266 ms 69.55.192.102
4 2026-08-25 01:39 639232182496008942
129 ms 69.55.192.102
3 2026-08-25 01:22 639232172197053132
252 ms 69.55.192.102
2 2026-08-25 00:28 639232140250307418
2144 ms 69.55.192.102
1 2026-08-25 00:11 639232129927860324
265 ms 69.55.192.102