DNS response history for ns4.cloudkami.com

ns4.cloudkami.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 33 DNS check records, 33 successful responses, 0 failed responses, and 209 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 ns4.cloudkami.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

209 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

92.123.95.4

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns4.cloudkami.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
33 2026-08-27 10:31 639234233269654413
11 ms 92.123.95.4
32 2026-08-27 10:14 639234222943951923
118 ms 92.123.95.4
31 2026-08-27 09:56 639234212558002823
67 ms 92.123.95.4
30 2026-08-27 09:39 639234202117531850
56 ms 92.123.95.4
29 2026-08-27 09:21 639234191649612722
140 ms 92.123.95.4
28 2026-08-27 09:04 639234181105879568
33 ms 92.123.95.4
27 2026-08-27 08:47 639234170713214496
40 ms 92.123.95.4
26 2026-08-27 08:29 639234160341037652
69 ms 92.123.95.4
25 2026-08-27 08:12 639234149799404224
29 ms 92.123.95.4
24 2026-08-27 07:55 639234139553286469
73 ms 92.123.95.4
23 2026-08-27 07:01 639234107183588293
137 ms 92.123.95.4
22 2026-08-27 06:44 639234096905435724
123 ms 92.123.95.4
21 2026-08-27 06:26 639234086579410775
166 ms 92.123.95.4
20 2026-08-27 06:09 639234076291157956
28 ms 92.123.95.4
19 2026-08-27 05:52 639234065981939454
130 ms 92.123.95.4
18 2026-08-27 05:35 639234055548642997
85 ms 92.123.95.4
17 2026-08-27 05:18 639234045267979603
115 ms 92.123.95.4
16 2026-08-27 05:00 639234034999717463
156 ms 92.123.95.4
15 2026-08-27 04:43 639234024739225358
32 ms 92.123.95.4
14 2026-08-27 04:26 639234014311170162
124 ms 92.123.95.4
13 2026-08-27 04:08 639234003806017640
2037 ms 92.123.95.4
12 2026-08-27 03:51 639233993356203030
135 ms 92.123.95.4
11 2026-08-27 02:58 639233961301716608
2025 ms 92.123.95.4
10 2026-08-27 02:40 639233950834200647
69 ms 92.123.95.4
9 2026-08-27 02:23 639233940431849026
201 ms 92.123.95.4
8 2026-08-27 02:06 639233930110596398
47 ms 92.123.95.4
7 2026-08-27 01:48 639233919705434540
87 ms 92.123.95.4
6 2026-08-27 01:31 639233909452807845
51 ms 92.123.95.4
5 2026-08-27 01:14 639233899096420820
77 ms 92.123.95.4
4 2026-08-27 00:57 639233888707824939
46 ms 92.123.95.4
3 2026-08-27 00:40 639233878461203802
4 ms 92.123.95.4
2 2026-08-27 00:22 639233868060868209
294 ms 92.123.95.4
1 2026-08-27 00:05 639233857450922991
93 ms 92.123.95.4