DNS response history for ns2.cbzauto.com

ns2.cbzauto.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 38 DNS check records, 38 successful responses, 0 failed responses, and 516 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.cbzauto.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

516 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

24.227.174.91

Most recently resolved hosting IP on selected date

Successful Responses

38

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.cbzauto.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
38 2026-08-24 15:53 639231828211839931
294 ms 24.227.174.91
37 2026-08-24 15:36 639231818080917481
280 ms 24.227.174.91
36 2026-08-24 15:19 639231807961539652
279 ms 24.227.174.91
35 2026-08-24 15:02 639231797631669865
1809 ms 24.227.174.91
34 2026-08-24 14:09 639231765923559455
282 ms 24.227.174.91
33 2026-08-24 13:52 639231755868832964
284 ms 24.227.174.91
32 2026-08-24 13:35 639231745628278877
1648 ms 24.227.174.91
31 2026-08-24 13:18 639231735407682062
280 ms 24.227.174.91
30 2026-08-24 12:25 639231703815441688
293 ms 24.227.174.91
29 2026-08-24 12:09 639231693747052549
3 ms 24.227.174.91
28 2026-08-24 11:52 639231683712487276
291 ms 24.227.174.91
27 2026-08-24 11:35 639231673513573868
282 ms 24.227.174.91
26 2026-08-24 10:42 639231641791249939
4 ms 24.227.174.91
25 2026-08-24 10:26 639231631866211033
288 ms 24.227.174.91
24 2026-08-24 10:09 639231621644955316
152 ms 24.227.174.91
23 2026-08-24 09:52 639231611478799259
304 ms 24.227.174.91
22 2026-08-24 08:59 639231579923718211
280 ms 24.227.174.91
21 2026-08-24 08:42 639231569810702936
2 ms 24.227.174.91
20 2026-08-24 08:25 639231559762411619
278 ms 24.227.174.91
19 2026-08-24 08:09 639231549663595407
3099 ms 24.227.174.91
18 2026-08-24 07:16 639231518076817246
3726 ms 24.227.174.91
17 2026-08-24 07:00 639231508078650885
1647 ms 24.227.174.91
16 2026-08-24 06:43 639231498210697093
13 ms 24.227.174.91
15 2026-08-24 06:26 639231488109699360
278 ms 24.227.174.91
14 2026-08-24 05:34 639231456772510692
3 ms 24.227.174.91
13 2026-08-24 05:17 639231447084631185
299 ms 24.227.174.91
12 2026-08-24 05:01 639231437208519473
2 ms 24.227.174.91
11 2026-08-24 04:44 639231427209627490
294 ms 24.227.174.91
10 2026-08-24 03:52 639231395791246644
3 ms 24.227.174.91
9 2026-08-24 03:36 639231386075551458
11 ms 24.227.174.91
8 2026-08-24 03:20 639231376208713791
2 ms 24.227.174.91
7 2026-08-24 03:03 639231366170589276
284 ms 24.227.174.91
6 2026-08-24 02:10 639231334732159368
295 ms 24.227.174.91
5 2026-08-24 01:54 639231325035670078
3 ms 24.227.174.91
4 2026-08-24 01:38 639231315132253837
1879 ms 24.227.174.91
3 2026-08-24 01:21 639231305014280808
277 ms 24.227.174.91
2 2026-08-24 00:29 639231273779380675
163 ms 24.227.174.91
1 2026-08-24 00:13 639231264180839154
3 ms 24.227.174.91