DNS response history for ns4.bitss.cloud

ns4.bitss.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 185 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.bitss.cloud.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

185 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.47.58.145

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 ns4.bitss.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:06 639234253963286387
34 ms 89.47.58.145
34 2026-08-27 10:49 639234243654907465
39 ms 89.47.58.145
33 2026-08-27 10:32 639234233269654413
49 ms 89.47.58.145
32 2026-08-27 10:15 639234222943951923
45 ms 89.47.58.145
31 2026-08-27 09:57 639234212558002823
132 ms 89.47.58.145
30 2026-08-27 09:40 639234202117531850
45 ms 89.47.58.145
29 2026-08-27 09:22 639234191649612722
66 ms 89.47.58.145
28 2026-08-27 09:05 639234181105879568
48 ms 89.47.58.145
27 2026-08-27 08:48 639234170713214496
16 ms 89.47.58.145
26 2026-08-27 08:30 639234160341037652
11 ms 89.47.58.145
25 2026-08-27 08:13 639234149799404224
47 ms 89.47.58.145
24 2026-08-27 07:56 639234139553286469
55 ms 89.47.58.145
23 2026-08-27 07:02 639234107183588293
29 ms 89.47.58.145
22 2026-08-27 06:45 639234096905435724
79 ms 89.47.58.145
21 2026-08-27 06:28 639234086579410775
26 ms 89.47.58.145
20 2026-08-27 06:10 639234076291157956
40 ms 89.47.58.145
19 2026-08-27 05:53 639234065981939454
13 ms 89.47.58.145
18 2026-08-27 05:36 639234055548642997
1040 ms 89.47.58.145
17 2026-08-27 05:19 639234045267979603
24 ms 89.47.58.145
16 2026-08-27 05:02 639234034999717463
11 ms 89.47.58.145
15 2026-08-27 04:44 639234024739225358
50 ms 89.47.58.145
14 2026-08-27 04:27 639234014311170162
31 ms 89.47.58.145
13 2026-08-27 04:09 639234003806017640
24 ms 89.47.58.145
12 2026-08-27 03:52 639233993356203030
36 ms 89.47.58.145
11 2026-08-27 02:59 639233961301716608
24 ms 89.47.58.145
10 2026-08-27 02:41 639233950834200647
12 ms 89.47.58.145
9 2026-08-27 02:24 639233940431849026
17 ms 89.47.58.145
8 2026-08-27 02:07 639233930110596398
24 ms 89.47.58.145
7 2026-08-27 01:49 639233919705434540
21 ms 89.47.58.145
6 2026-08-27 01:32 639233909452807845
72 ms 89.47.58.145
5 2026-08-27 01:15 639233899096420820
24 ms 89.47.58.145
4 2026-08-27 00:58 639233888707824939
2068 ms 89.47.58.145
3 2026-08-27 00:41 639233878461203802
2047 ms 89.47.58.145
2 2026-08-27 00:23 639233868060868209
45 ms 89.47.58.145
1 2026-08-27 00:06 639233857450922991
140 ms 89.47.58.145