DNS response history for ns2.crispbot.com

ns2.crispbot.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-30. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 510 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.crispbot.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

510 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

223.235.16.65

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-08-30 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
37 2026-08-30 12:08 639236878057367680
4 ms 223.235.16.65
36 2026-08-30 11:51 639236867916029489
371 ms 223.235.16.65
35 2026-08-30 11:34 639236858088772005
266 ms 223.235.16.65
34 2026-08-30 11:17 639236848158742395
344 ms 223.235.16.65
33 2026-08-30 11:01 639236838137395574
348 ms 223.235.16.65
32 2026-08-30 10:44 639236827967386881
2273 ms 223.235.16.65
31 2026-08-30 10:27 639236817708615077
387 ms 223.235.16.65
30 2026-08-30 09:34 639236785770651804
3 ms 223.235.16.65
29 2026-08-30 09:17 639236775820686373
253 ms 223.235.16.65
28 2026-08-30 09:00 639236765768339082
3 ms 223.235.16.65
27 2026-08-30 08:43 639236755602384085
5 ms 223.235.16.65
26 2026-08-30 08:26 639236745600094925
365 ms 223.235.16.65
25 2026-08-30 08:10 639236735311262753
339 ms 223.235.16.65
24 2026-08-30 07:53 639236724996745235
369 ms 223.235.16.65
23 2026-08-30 07:35 639236714839899761
322 ms 223.235.16.65
22 2026-08-30 07:19 639236704748431488
419 ms 223.235.16.65
21 2026-08-30 07:02 639236694430128550
432 ms 223.235.16.65
20 2026-08-30 06:44 639236684143292417
3 ms 223.235.16.65
19 2026-08-30 06:27 639236673972499943
382 ms 223.235.16.65
18 2026-08-30 05:34 639236642126522802
6 ms 223.235.16.65
17 2026-08-30 05:18 639236632183518198
409 ms 223.235.16.65
16 2026-08-30 05:01 639236622289312589
396 ms 223.235.16.65
15 2026-08-30 04:45 639236612490676525
2218 ms 223.235.16.65
14 2026-08-30 04:28 639236602582494852
387 ms 223.235.16.65
13 2026-08-30 04:12 639236592511706469
430 ms 223.235.16.65
12 2026-08-30 03:55 639236582441006869
335 ms 223.235.16.65
11 2026-08-30 03:38 639236572478785089
380 ms 223.235.16.65
10 2026-08-30 03:22 639236562556749999
2206 ms 223.235.16.65
9 2026-08-30 03:05 639236552353482281
343 ms 223.235.16.65
8 2026-08-30 02:48 639236542188881607
2323 ms 223.235.16.65
7 2026-08-30 02:31 639236531885440105
395 ms 223.235.16.65
6 2026-08-30 01:37 639236499922985383
333 ms 223.235.16.65
5 2026-08-30 01:20 639236489713594431
338 ms 223.235.16.65
4 2026-08-30 01:04 639236479750443901
393 ms 223.235.16.65
3 2026-08-30 00:47 639236469719936375
397 ms 223.235.16.65
2 2026-08-30 00:30 639236459579244885
339 ms 223.235.16.65
1 2026-08-30 00:13 639236449582837549
341 ms 223.235.16.65