DNS response history for ns200.aj3018.bid

ns200.aj3018.bid 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 410 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 ns200.aj3018.bid.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

410 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.124.115.200

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 ns200.aj3018.bid

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:23 639231703815441688
141 ms 212.124.115.200
29 2026-08-24 12:07 639231693747052549
251 ms 212.124.115.200
28 2026-08-24 11:50 639231683712487276
135 ms 212.124.115.200
27 2026-08-24 11:33 639231673513573868
254 ms 212.124.115.200
26 2026-08-24 10:40 639231641791249939
240 ms 212.124.115.200
25 2026-08-24 10:24 639231631866211033
247 ms 212.124.115.200
24 2026-08-24 10:07 639231621644955316
246 ms 212.124.115.200
23 2026-08-24 09:50 639231611478799259
101 ms 212.124.115.200
22 2026-08-24 08:57 639231579923718211
134 ms 212.124.115.200
21 2026-08-24 08:40 639231569810702936
247 ms 212.124.115.200
20 2026-08-24 08:23 639231559762411619
243 ms 212.124.115.200
19 2026-08-24 08:07 639231549663595407
248 ms 212.124.115.200
18 2026-08-24 07:14 639231518076817246
246 ms 212.124.115.200
17 2026-08-24 06:58 639231508078650885
249 ms 212.124.115.200
16 2026-08-24 06:41 639231498210697093
2106 ms 212.124.115.200
15 2026-08-24 06:24 639231488109699360
4139 ms 212.124.115.200
14 2026-08-24 05:32 639231456772510692
245 ms 212.124.115.200
13 2026-08-24 05:16 639231447084631185
241 ms 212.124.115.200
12 2026-08-24 04:59 639231437208519473
239 ms 212.124.115.200
11 2026-08-24 04:43 639231427209627490
238 ms 212.124.115.200
10 2026-08-24 03:50 639231395791246644
244 ms 212.124.115.200
9 2026-08-24 03:34 639231386075551458
127 ms 212.124.115.200
8 2026-08-24 03:18 639231376208713791
241 ms 212.124.115.200
7 2026-08-24 03:01 639231366170589276
102 ms 212.124.115.200
6 2026-08-24 02:08 639231334732159368
253 ms 212.124.115.200
5 2026-08-24 01:52 639231325035670078
249 ms 212.124.115.200
4 2026-08-24 01:36 639231315132253837
191 ms 212.124.115.200
3 2026-08-24 01:19 639231305014280808
241 ms 212.124.115.200
2 2026-08-24 00:27 639231273779380675
241 ms 212.124.115.200
1 2026-08-24 00:11 639231264180839154
236 ms 212.124.115.200