DNS response history for ns2.affluentcbt.com

ns2.affluentcbt.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 35 DNS check records, 34 successful responses, 1 failed responses, and 231 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.affluentcbt.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

231 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

77.68.16.235

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.affluentcbt.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
35 2026-08-27 11:04 639234253963286387
76 ms 77.68.16.235
34 2026-08-27 10:47 639234243654907465
66 ms 77.68.16.235
33 2026-08-27 10:30 639234233269654413
66 ms 77.68.16.235
32 2026-08-27 10:13 639234222943951923
42 ms 77.68.16.235
31 2026-08-27 09:55 639234212558002823
2061 ms 77.68.16.235
30 2026-08-27 09:38 639234202117531850
78 ms 77.68.16.235
29 2026-08-27 09:21 639234191649612722
83 ms 77.68.16.235
28 2026-08-27 09:03 639234181105879568
2057 ms 77.68.16.235
27 2026-08-27 08:46 639234170713214496
39 ms 77.68.16.235
26 2026-08-27 08:28 639234160341037652
83 ms 77.68.16.235
25 2026-08-27 08:11 639234149799404224
40 ms 77.68.16.235
24 2026-08-27 07:54 639234139553286469
61 ms 77.68.16.235
23 2026-08-27 07:00 639234107183588293
9 ms 77.68.16.235
22 2026-08-27 06:43 639234096905435724
65 ms 77.68.16.235
21 2026-08-27 06:26 639234086579410775
33 ms 77.68.16.235
20 2026-08-27 06:08 639234076291157956
37 ms 77.68.16.235
19 2026-08-27 05:51 639234065981939454
45 ms 77.68.16.235
18 2026-08-27 05:34 639234055548642997
31 ms 77.68.16.235
17 2026-08-27 05:17 639234045267979603
39 ms 77.68.16.235
16 2026-08-27 05:00 639234034999717463
64 ms 77.68.16.235
15 2026-08-27 04:43 639234024739225358
79 ms 77.68.16.235
14 2026-08-27 04:25 639234014311170162
59 ms 77.68.16.235
13 2026-08-27 04:08 639234003806017640
96 ms 77.68.16.235
12 2026-08-27 03:50 639233993356203030
79 ms 77.68.16.235
11 2026-08-27 02:57 639233961301716608
-
10 2026-08-27 02:39 639233950834200647
39 ms 77.68.16.235
9 2026-08-27 02:22 639233940431849026
60 ms 77.68.16.235
8 2026-08-27 02:05 639233930110596398
36 ms 77.68.16.235
7 2026-08-27 01:47 639233919705434540
77 ms 77.68.16.235
6 2026-08-27 01:30 639233909452807845
32 ms 77.68.16.235
5 2026-08-27 01:13 639233899096420820
9 ms 77.68.16.235
4 2026-08-27 00:56 639233888707824939
29 ms 77.68.16.235
3 2026-08-27 00:39 639233878461203802
73 ms 77.68.16.235
2 2026-08-27 00:21 639233868060868209
59 ms 77.68.16.235
1 2026-08-27 00:04 639233857450922991
2038 ms 77.68.16.235