DNS response history for ns2.cr366.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

567 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.99.253.173

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

Showing DNS history for 2026-08-31 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-31 12:11 639237742927117371
645 ms 139.99.253.173
36 2026-08-31 11:54 639237732538256235
643 ms 139.99.253.173
35 2026-08-31 11:37 639237722025682013
654 ms 139.99.253.173
34 2026-08-31 11:19 639237711568720101
635 ms 139.99.253.173
33 2026-08-31 11:02 639237701119461876
634 ms 139.99.253.173
32 2026-08-31 10:44 639237690759595513
645 ms 139.99.253.173
31 2026-08-31 10:27 639237680122296836
638 ms 139.99.253.173
30 2026-08-31 09:33 639237647999458954
631 ms 139.99.253.173
29 2026-08-31 09:16 639237637680951774
647 ms 139.99.253.173
28 2026-08-31 08:59 639237627437728712
648 ms 139.99.253.173
27 2026-08-31 08:42 639237617127808241
639 ms 139.99.253.173
26 2026-08-31 08:25 639237606990101394
647 ms 139.99.253.173
25 2026-08-31 08:08 639237596595480036
4 ms 139.99.253.173
24 2026-08-31 07:50 639237586261012001
4 ms 139.99.253.173
23 2026-08-31 07:33 639237576047657695
643 ms 139.99.253.173
22 2026-08-31 07:16 639237565832936443
630 ms 139.99.253.173
21 2026-08-31 06:59 639237555466329546
6 ms 139.99.253.173
20 2026-08-31 06:42 639237545032411072
3 ms 139.99.253.173
19 2026-08-31 06:24 639237534469438634
638 ms 139.99.253.173
18 2026-08-31 05:30 639237502279296801
644 ms 139.99.253.173
17 2026-08-31 05:13 639237492362730124
3 ms 139.99.253.173
16 2026-08-31 04:57 639237482311584319
2007 ms 139.99.253.173
15 2026-08-31 04:40 639237472150685594
631 ms 139.99.253.173
14 2026-08-31 04:23 639237462055295430
2302 ms 139.99.253.173
13 2026-08-31 04:06 639237452089913890
2 ms 139.99.253.173
12 2026-08-31 03:50 639237441972654103
2 ms 139.99.253.173
11 2026-08-31 03:33 639237432052396478
2 ms 139.99.253.173
10 2026-08-31 03:16 639237422012990851
637 ms 139.99.253.173
9 2026-08-31 03:00 639237411889602012
643 ms 139.99.253.173
8 2026-08-31 02:43 639237401637354221
647 ms 139.99.253.173
7 2026-08-31 02:25 639237391412690360
631 ms 139.99.253.173
6 2026-08-31 01:33 639237359972957132
632 ms 139.99.253.173
5 2026-08-31 01:16 639237350032183979
634 ms 139.99.253.173
4 2026-08-31 01:00 639237340111452066
7 ms 139.99.253.173
3 2026-08-31 00:43 639237329967272514
630 ms 139.99.253.173
2 2026-08-31 00:26 639237319916508151
644 ms 139.99.253.173
1 2026-08-31 00:09 639237309944877243
635 ms 139.99.253.173