DNS response history for ns2cqs.name.com

ns2cqs.name.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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 201 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 ns2cqs.name.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

201 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

163.114.216.49

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2cqs.name.com

Showing DNS history for 2026-08-24 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
34 2026-08-24 13:56 639231765923559455
38 ms 163.114.216.49
33 2026-08-24 13:39 639231755868832964
13 ms 163.114.216.49
32 2026-08-24 13:22 639231745628278877
10 ms 163.114.216.49
31 2026-08-24 13:05 639231735407682062
77 ms 163.114.216.49
30 2026-08-24 12:13 639231703815441688
9 ms 163.114.216.49
29 2026-08-24 11:56 639231693747052549
9 ms 163.114.216.49
28 2026-08-24 11:39 639231683712487276
9 ms 163.114.216.49
27 2026-08-24 11:22 639231673513573868
2034 ms 163.114.216.49
26 2026-08-24 10:29 639231641791249939
4 ms 163.114.216.49
25 2026-08-24 10:13 639231631866211033
15 ms 163.114.216.49
24 2026-08-24 09:56 639231621644955316
29 ms 163.114.216.49
23 2026-08-24 09:39 639231611478799259
5 ms 163.114.216.49
22 2026-08-24 08:46 639231579923718211
2022 ms 163.114.216.49
21 2026-08-24 08:29 639231569810702936
34 ms 163.114.216.49
20 2026-08-24 08:13 639231559762411619
66 ms 163.114.216.49
19 2026-08-24 07:56 639231549663595407
51 ms 163.114.216.49
18 2026-08-24 07:03 639231518076817246
7 ms 163.114.216.49
17 2026-08-24 06:46 639231508078650885
55 ms 163.114.216.49
16 2026-08-24 06:30 639231498210697093
6 ms 163.114.216.49
15 2026-08-24 06:13 639231488109699360
37 ms 163.114.216.49
14 2026-08-24 05:21 639231456772510692
86 ms 163.114.216.49
13 2026-08-24 05:05 639231447084631185
20 ms 163.114.216.49
12 2026-08-24 04:48 639231437208519473
9 ms 163.114.216.49
11 2026-08-24 04:32 639231427209627490
2049 ms 163.114.216.49
10 2026-08-24 03:39 639231395791246644
7 ms 163.114.216.49
9 2026-08-24 03:23 639231386075551458
11 ms 163.114.216.49
8 2026-08-24 03:07 639231376208713791
25 ms 163.114.216.49
7 2026-08-24 02:50 639231366170589276
5 ms 163.114.216.49
6 2026-08-24 01:58 639231334732159368
15 ms 163.114.216.49
5 2026-08-24 01:41 639231325035670078
4 ms 163.114.216.49
4 2026-08-24 01:25 639231315132253837
12 ms 163.114.216.49
3 2026-08-24 01:08 639231305014280808
59 ms 163.114.216.49
2 2026-08-24 00:16 639231273779380675
6 ms 163.114.216.49
1 2026-08-24 00:00 639231264180839154
4 ms 163.114.216.49