DNS response history for ns2.cloudchain.link

ns2.cloudchain.link 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-27. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 180 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.cloudchain.link.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

180 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

132.145.98.163

Most recently resolved hosting IP on selected date

Successful Responses

29

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.cloudchain.link

Showing DNS history for 2026-08-27 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
29 2026-08-27 09:29 639234191649612722
117 ms 132.145.98.163
28 2026-08-27 09:11 639234181105879568
232 ms 132.145.98.163
27 2026-08-27 08:54 639234170713214496
250 ms 132.145.98.163
26 2026-08-27 08:37 639234160341037652
3 ms 132.145.98.163
25 2026-08-27 08:19 639234149799404224
113 ms 132.145.98.163
24 2026-08-27 08:02 639234139553286469
116 ms 132.145.98.163
23 2026-08-27 07:08 639234107183588293
233 ms 132.145.98.163
22 2026-08-27 06:51 639234096905435724
112 ms 132.145.98.163
21 2026-08-27 06:34 639234086579410775
123 ms 132.145.98.163
20 2026-08-27 06:17 639234076291157956
112 ms 132.145.98.163
19 2026-08-27 06:00 639234065981939454
113 ms 132.145.98.163
18 2026-08-27 05:42 639234055548642997
236 ms 132.145.98.163
17 2026-08-27 05:25 639234045267979603
242 ms 132.145.98.163
16 2026-08-27 05:08 639234034999717463
231 ms 132.145.98.163
15 2026-08-27 04:51 639234024739225358
234 ms 132.145.98.163
14 2026-08-27 04:34 639234014311170162
110 ms 132.145.98.163
13 2026-08-27 04:16 639234003806017640
234 ms 132.145.98.163
12 2026-08-27 03:58 639233993356203030
240 ms 132.145.98.163
11 2026-08-27 03:05 639233961301716608
228 ms 132.145.98.163
10 2026-08-27 02:48 639233950834200647
236 ms 132.145.98.163
9 2026-08-27 02:30 639233940431849026
229 ms 132.145.98.163
8 2026-08-27 02:13 639233930110596398
204 ms 132.145.98.163
7 2026-08-27 01:56 639233919705434540
233 ms 132.145.98.163
6 2026-08-27 01:39 639233909452807845
231 ms 132.145.98.163
5 2026-08-27 01:21 639233899096420820
128 ms 132.145.98.163
4 2026-08-27 01:04 639233888707824939
9 ms 132.145.98.163
3 2026-08-27 00:47 639233878461203802
228 ms 132.145.98.163
2 2026-08-27 00:30 639233868060868209
210 ms 132.145.98.163
1 2026-08-27 00:12 639233857450922991
231 ms 132.145.98.163