DNS response history for ns2.cb-range.com

ns2.cb-range.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 136 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.cb-range.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

136 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

93.157.86.8

Most recently resolved hosting IP on selected date

Successful Responses

36

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.cb-range.com

Showing DNS history for 2026-08-24 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
36 2026-08-24 15:14 639231807961539652
156 ms 93.157.86.8
35 2026-08-24 14:57 639231797631669865
130 ms 93.157.86.8
34 2026-08-24 14:04 639231765923559455
20 ms 93.157.86.8
33 2026-08-24 13:47 639231755868832964
14 ms 93.157.86.8
32 2026-08-24 13:30 639231745628278877
271 ms 93.157.86.8
31 2026-08-24 13:13 639231735407682062
138 ms 93.157.86.8
30 2026-08-24 12:20 639231703815441688
16 ms 93.157.86.8
29 2026-08-24 12:04 639231693747052549
3 ms 93.157.86.8
28 2026-08-24 11:47 639231683712487276
123 ms 93.157.86.8
27 2026-08-24 11:30 639231673513573868
113 ms 93.157.86.8
26 2026-08-24 10:37 639231641791249939
123 ms 93.157.86.8
25 2026-08-24 10:21 639231631866211033
78 ms 93.157.86.8
24 2026-08-24 10:04 639231621644955316
8 ms 93.157.86.8
23 2026-08-24 09:47 639231611478799259
133 ms 93.157.86.8
22 2026-08-24 08:54 639231579923718211
6 ms 93.157.86.8
21 2026-08-24 08:37 639231569810702936
135 ms 93.157.86.8
20 2026-08-24 08:20 639231559762411619
128 ms 93.157.86.8
19 2026-08-24 08:04 639231549663595407
5 ms 93.157.86.8
18 2026-08-24 07:11 639231518076817246
27 ms 93.157.86.8
17 2026-08-24 06:55 639231508078650885
136 ms 93.157.86.8
16 2026-08-24 06:38 639231498210697093
139 ms 93.157.86.8
15 2026-08-24 06:21 639231488109699360
3 ms 93.157.86.8
14 2026-08-24 05:29 639231456772510692
130 ms 93.157.86.8
13 2026-08-24 05:13 639231447084631185
69 ms 93.157.86.8
12 2026-08-24 04:56 639231437208519473
16 ms 93.157.86.8
11 2026-08-24 04:40 639231427209627490
123 ms 93.157.86.8
10 2026-08-24 03:47 639231395791246644
5 ms 93.157.86.8
9 2026-08-24 03:31 639231386075551458
79 ms 93.157.86.8
8 2026-08-24 03:15 639231376208713791
5 ms 93.157.86.8
7 2026-08-24 02:58 639231366170589276
7 ms 93.157.86.8
6 2026-08-24 02:06 639231334732159368
139 ms 93.157.86.8
5 2026-08-24 01:49 639231325035670078
129 ms 93.157.86.8
4 2026-08-24 01:33 639231315132253837
2129 ms 93.157.86.8
3 2026-08-24 01:16 639231305014280808
138 ms 93.157.86.8
2 2026-08-24 00:24 639231273779380675
3 ms 93.157.86.8
1 2026-08-24 00:08 639231264180839154
18 ms 93.157.86.8