DNS response history for ns.brandma.cn

ns.brandma.cn 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 37 DNS check records, 37 successful responses, 0 failed responses, and 399 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 ns.brandma.cn.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

399 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.208.24.170

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns.brandma.cn

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
37 2026-08-24 15:37 639231818080917481
536 ms 125.208.24.170
36 2026-08-24 15:20 639231807961539652
3 ms 125.208.24.170
35 2026-08-24 15:03 639231797631669865
659 ms 125.208.24.170
34 2026-08-24 14:10 639231765923559455
3 ms 125.208.24.170
33 2026-08-24 13:54 639231755868832964
541 ms 125.208.24.170
32 2026-08-24 13:37 639231745628278877
535 ms 125.208.24.170
31 2026-08-24 13:19 639231735407682062
2 ms 125.208.24.170
30 2026-08-24 12:27 639231703815441688
563 ms 125.208.24.170
29 2026-08-24 12:10 639231693747052549
527 ms 125.208.24.170
28 2026-08-24 11:53 639231683712487276
553 ms 125.208.24.170
27 2026-08-24 11:36 639231673513573868
545 ms 125.208.24.170
26 2026-08-24 10:43 639231641791249939
2 ms 125.208.24.170
25 2026-08-24 10:27 639231631866211033
900 ms 125.208.24.170
24 2026-08-24 10:10 639231621644955316
671 ms 125.208.24.170
23 2026-08-24 09:53 639231611478799259
656 ms 125.208.24.170
22 2026-08-24 09:00 639231579923718211
3 ms 125.208.24.170
21 2026-08-24 08:44 639231569810702936
3 ms 125.208.24.170
20 2026-08-24 08:27 639231559762411619
1433 ms 125.208.24.170
19 2026-08-24 08:10 639231549663595407
3 ms 125.208.24.170
18 2026-08-24 07:17 639231518076817246
552 ms 125.208.24.170
17 2026-08-24 07:01 639231508078650885
677 ms 125.208.24.170
16 2026-08-24 06:44 639231498210697093
549 ms 125.208.24.170
15 2026-08-24 06:27 639231488109699360
5 ms 125.208.24.170
14 2026-08-24 05:35 639231456772510692
542 ms 125.208.24.170
13 2026-08-24 05:19 639231447084631185
555 ms 125.208.24.170
12 2026-08-24 05:02 639231437208519473
630 ms 125.208.24.170
11 2026-08-24 04:46 639231427209627490
592 ms 125.208.24.170
10 2026-08-24 03:53 639231395791246644
4 ms 125.208.24.170
9 2026-08-24 03:37 639231386075551458
3 ms 125.208.24.170
8 2026-08-24 03:21 639231376208713791
247 ms 125.208.24.170
7 2026-08-24 03:04 639231366170589276
599 ms 125.208.24.170
6 2026-08-24 02:12 639231334732159368
3 ms 125.208.24.170
5 2026-08-24 01:55 639231325035670078
3 ms 125.208.24.170
4 2026-08-24 01:39 639231315132253837
539 ms 125.208.24.170
3 2026-08-24 01:22 639231305014280808
567 ms 125.208.24.170
2 2026-08-24 00:30 639231273779380675
547 ms 125.208.24.170
1 2026-08-24 00:14 639231264180839154
3 ms 125.208.24.170