DNS response history for ns1.bringingkingtochina.com

ns1.bringingkingtochina.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 30 DNS check records, 30 successful responses, 0 failed responses, and 108 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 ns1.bringingkingtochina.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

108 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.132.63.206

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.bringingkingtochina.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
30 2026-08-24 12:17 639231703815441688
34 ms 164.132.63.206
29 2026-08-24 12:00 639231693747052549
66 ms 164.132.63.206
28 2026-08-24 11:43 639231683712487276
44 ms 164.132.63.206
27 2026-08-24 11:27 639231673513573868
45 ms 164.132.63.206
26 2026-08-24 10:33 639231641791249939
17 ms 164.132.63.206
25 2026-08-24 10:17 639231631866211033
12 ms 164.132.63.206
24 2026-08-24 10:00 639231621644955316
93 ms 164.132.63.206
23 2026-08-24 09:43 639231611478799259
39 ms 164.132.63.206
22 2026-08-24 08:51 639231579923718211
16 ms 164.132.63.206
21 2026-08-24 08:34 639231569810702936
34 ms 164.132.63.206
20 2026-08-24 08:17 639231559762411619
48 ms 164.132.63.206
19 2026-08-24 08:00 639231549663595407
43 ms 164.132.63.206
18 2026-08-24 07:07 639231518076817246
2134 ms 164.132.63.206
17 2026-08-24 06:51 639231508078650885
25 ms 164.132.63.206
16 2026-08-24 06:34 639231498210697093
47 ms 164.132.63.206
15 2026-08-24 06:18 639231488109699360
47 ms 164.132.63.206
14 2026-08-24 05:25 639231456772510692
55 ms 164.132.63.206
13 2026-08-24 05:09 639231447084631185
41 ms 164.132.63.206
12 2026-08-24 04:53 639231437208519473
9 ms 164.132.63.206
11 2026-08-24 04:36 639231427209627490
16 ms 164.132.63.206
10 2026-08-24 03:44 639231395791246644
40 ms 164.132.63.206
9 2026-08-24 03:27 639231386075551458
68 ms 164.132.63.206
8 2026-08-24 03:11 639231376208713791
39 ms 164.132.63.206
7 2026-08-24 02:54 639231366170589276
39 ms 164.132.63.206
6 2026-08-24 02:02 639231334732159368
34 ms 164.132.63.206
5 2026-08-24 01:46 639231325035670078
33 ms 164.132.63.206
4 2026-08-24 01:29 639231315132253837
10 ms 164.132.63.206
3 2026-08-24 01:12 639231305014280808
31 ms 164.132.63.206
2 2026-08-24 00:20 639231273779380675
16 ms 164.132.63.206
1 2026-08-24 00:04 639231264180839154
50 ms 164.132.63.206