DNS response history for ns2.adbeardigital.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

112 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

46.31.145.159

Most recently resolved hosting IP on selected date

Successful Responses

26

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.adbeardigital.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
26 2026-08-24 10:38 639231641791249939
6 ms 46.31.145.159
25 2026-08-24 10:21 639231631866211033
5 ms 46.31.145.159
24 2026-08-24 10:05 639231621644955316
40 ms 46.31.145.159
23 2026-08-24 09:48 639231611478799259
78 ms 46.31.145.159
22 2026-08-24 08:55 639231579923718211
118 ms 46.31.145.159
21 2026-08-24 08:38 639231569810702936
272 ms 46.31.145.159
20 2026-08-24 08:21 639231559762411619
76 ms 46.31.145.159
19 2026-08-24 08:04 639231549663595407
6 ms 46.31.145.159
18 2026-08-24 07:12 639231518076817246
108 ms 46.31.145.159
17 2026-08-24 06:55 639231508078650885
3 ms 46.31.145.159
16 2026-08-24 06:39 639231498210697093
84 ms 46.31.145.159
15 2026-08-24 06:22 639231488109699360
78 ms 46.31.145.159
14 2026-08-24 05:30 639231456772510692
3 ms 46.31.145.159
13 2026-08-24 05:14 639231447084631185
352 ms 46.31.145.159
12 2026-08-24 04:57 639231437208519473
111 ms 46.31.145.159
11 2026-08-24 04:40 639231427209627490
59 ms 46.31.145.159
10 2026-08-24 03:48 639231395791246644
4 ms 46.31.145.159
9 2026-08-24 03:32 639231386075551458
3 ms 46.31.145.159
8 2026-08-24 03:16 639231376208713791
39 ms 46.31.145.159
7 2026-08-24 02:59 639231366170589276
177 ms 46.31.145.159
6 2026-08-24 02:06 639231334732159368
3 ms 46.31.145.159
5 2026-08-24 01:50 639231325035670078
179 ms 46.31.145.159
4 2026-08-24 01:34 639231315132253837
438 ms 46.31.145.159
3 2026-08-24 01:17 639231305014280808
317 ms 46.31.145.159
2 2026-08-24 00:25 639231273779380675
281 ms 46.31.145.159
1 2026-08-24 00:09 639231264180839154
74 ms 46.31.145.159