DNS response history for ns2.crisance.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

156 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

13.205.42.144

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.crisance.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
28 2026-08-25 09:42 639232471861770303
160 ms 13.205.42.144
27 2026-08-25 09:25 639232461630217327
6 ms 13.205.42.144
26 2026-08-25 09:08 639232451282965990
161 ms 13.205.42.144
25 2026-08-25 08:51 639232440814614938
187 ms 13.205.42.144
24 2026-08-25 08:33 639232430410720425
309 ms 13.205.42.144
23 2026-08-25 08:16 639232420003096185
171 ms 13.205.42.144
22 2026-08-25 07:59 639232409467287444
175 ms 13.205.42.144
21 2026-08-25 07:41 639232399077195997
311 ms 13.205.42.144
20 2026-08-25 07:24 639232388731528337
7 ms 13.205.42.144
19 2026-08-25 07:06 639232378288598612
153 ms 13.205.42.144
18 2026-08-25 06:13 639232346196373643
17 ms 13.205.42.144
17 2026-08-25 05:56 639232336112370741
301 ms 13.205.42.144
16 2026-08-25 05:39 639232326146508970
166 ms 13.205.42.144
15 2026-08-25 05:23 639232316189381720
26 ms 13.205.42.144
14 2026-08-25 05:06 639232306217998913
19 ms 13.205.42.144
13 2026-08-25 04:50 639232296255744174
8 ms 13.205.42.144
12 2026-08-25 04:33 639232286095760789
180 ms 13.205.42.144
11 2026-08-25 04:16 639232276086186273
172 ms 13.205.42.144
10 2026-08-25 03:59 639232265900986425
158 ms 13.205.42.144
9 2026-08-25 03:42 639232255723518075
252 ms 13.205.42.144
8 2026-08-25 03:25 639232245484452890
164 ms 13.205.42.144
7 2026-08-25 03:08 639232235157175331
153 ms 13.205.42.144
6 2026-08-25 02:15 639232203197189095
309 ms 13.205.42.144
5 2026-08-25 01:57 639232192844564298
201 ms 13.205.42.144
4 2026-08-25 01:40 639232182496008942
152 ms 13.205.42.144
3 2026-08-25 01:23 639232172197053132
151 ms 13.205.42.144
2 2026-08-25 00:30 639232140250307418
9 ms 13.205.42.144
1 2026-08-25 00:13 639232129927860324
278 ms 13.205.42.144