DNS response history for ns2.cloudprime.cloud

ns2.cloudprime.cloud 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 35 DNS check records, 35 successful responses, 0 failed responses, and 90 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.cloudprime.cloud.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

90 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

201.46.120.101

Most recently resolved hosting IP on selected date

Successful Responses

35

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.cloudprime.cloud

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
35 2026-08-27 11:04 639234253963286387
9 ms 201.46.120.101
34 2026-08-27 10:47 639234243654907465
4 ms 201.46.120.101
33 2026-08-27 10:30 639234233269654413
196 ms 201.46.120.101
32 2026-08-27 10:12 639234222943951923
129 ms 201.46.120.101
31 2026-08-27 09:55 639234212558002823
48 ms 201.46.120.101
30 2026-08-27 09:38 639234202117531850
27 ms 201.46.120.101
29 2026-08-27 09:20 639234191649612722
27 ms 201.46.120.101
28 2026-08-27 09:03 639234181105879568
34 ms 201.46.120.101
27 2026-08-27 08:45 639234170713214496
35 ms 201.46.120.101
26 2026-08-27 08:28 639234160341037652
44 ms 201.46.120.101
25 2026-08-27 08:11 639234149799404224
185 ms 201.46.120.101
24 2026-08-27 07:54 639234139553286469
43 ms 201.46.120.101
23 2026-08-27 07:00 639234107183588293
194 ms 201.46.120.101
22 2026-08-27 06:43 639234096905435724
240 ms 201.46.120.101
21 2026-08-27 06:25 639234086579410775
21 ms 201.46.120.101
20 2026-08-27 06:08 639234076291157956
86 ms 201.46.120.101
19 2026-08-27 05:51 639234065981939454
53 ms 201.46.120.101
18 2026-08-27 05:34 639234055548642997
45 ms 201.46.120.101
17 2026-08-27 05:17 639234045267979603
182 ms 201.46.120.101
16 2026-08-27 04:59 639234034999717463
75 ms 201.46.120.101
15 2026-08-27 04:42 639234024739225358
190 ms 201.46.120.101
14 2026-08-27 04:25 639234014311170162
47 ms 201.46.120.101
13 2026-08-27 04:07 639234003806017640
213 ms 201.46.120.101
12 2026-08-27 03:50 639233993356203030
102 ms 201.46.120.101
11 2026-08-27 02:57 639233961301716608
21 ms 201.46.120.101
10 2026-08-27 02:39 639233950834200647
31 ms 201.46.120.101
9 2026-08-27 02:22 639233940431849026
166 ms 201.46.120.101
8 2026-08-27 02:05 639233930110596398
27 ms 201.46.120.101
7 2026-08-27 01:47 639233919705434540
39 ms 201.46.120.101
6 2026-08-27 01:30 639233909452807845
46 ms 201.46.120.101
5 2026-08-27 01:13 639233899096420820
122 ms 201.46.120.101
4 2026-08-27 00:56 639233888707824939
27 ms 201.46.120.101
3 2026-08-27 00:38 639233878461203802
188 ms 201.46.120.101
2 2026-08-27 00:21 639233868060868209
43 ms 201.46.120.101
1 2026-08-27 00:03 639233857450922991
197 ms 201.46.120.101