DNS response history for ns1.cloud-be.com

ns1.cloud-be.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 336 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 ns1.cloud-be.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.55.38.228

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 ns1.cloud-be.com

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
34 2026-08-27 10:46 639234243654907465
44 ms 162.55.38.228
33 2026-08-27 10:29 639234233269654413
9 ms 162.55.38.228
32 2026-08-27 10:11 639234222943951923
37 ms 162.55.38.228
31 2026-08-27 09:54 639234212558002823
2026 ms 162.55.38.228
30 2026-08-27 09:37 639234202117531850
65 ms 162.55.38.228
29 2026-08-27 09:19 639234191649612722
40 ms 162.55.38.228
28 2026-08-27 09:02 639234181105879568
2035 ms 162.55.38.228
27 2026-08-27 08:44 639234170713214496
38 ms 162.55.38.228
26 2026-08-27 08:27 639234160341037652
37 ms 162.55.38.228
25 2026-08-27 08:09 639234149799404224
88 ms 162.55.38.228
24 2026-08-27 07:52 639234139553286469
104 ms 162.55.38.228
23 2026-08-27 06:59 639234107183588293
50 ms 162.55.38.228
22 2026-08-27 06:41 639234096905435724
39 ms 162.55.38.228
21 2026-08-27 06:24 639234086579410775
32 ms 162.55.38.228
20 2026-08-27 06:07 639234076291157956
35 ms 162.55.38.228
19 2026-08-27 05:50 639234065981939454
60 ms 162.55.38.228
18 2026-08-27 05:32 639234055548642997
76 ms 162.55.38.228
17 2026-08-27 05:15 639234045267979603
45 ms 162.55.38.228
16 2026-08-27 04:58 639234034999717463
31 ms 162.55.38.228
15 2026-08-27 04:41 639234024739225358
31 ms 162.55.38.228
14 2026-08-27 04:24 639234014311170162
2023 ms 162.55.38.228
13 2026-08-27 04:06 639234003806017640
27 ms 162.55.38.228
12 2026-08-27 03:49 639233993356203030
35 ms 162.55.38.228
11 2026-08-27 02:55 639233961301716608
28 ms 162.55.38.228
10 2026-08-27 02:38 639233950834200647
4030 ms 162.55.38.228
9 2026-08-27 02:21 639233940431849026
67 ms 162.55.38.228
8 2026-08-27 02:03 639233930110596398
17 ms 162.55.38.228
7 2026-08-27 01:46 639233919705434540
33 ms 162.55.38.228
6 2026-08-27 01:29 639233909452807845
31 ms 162.55.38.228
5 2026-08-27 01:12 639233899096420820
67 ms 162.55.38.228
4 2026-08-27 00:54 639233888707824939
27 ms 162.55.38.228
3 2026-08-27 00:37 639233878461203802
25 ms 162.55.38.228
2 2026-08-27 00:20 639233868060868209
40 ms 162.55.38.228
1 2026-08-27 00:02 639233857450922991
51 ms 162.55.38.228