DNS response history for ns3.beebytecdn.com

ns3.beebytecdn.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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 322 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 ns3.beebytecdn.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

322 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.168.230.171

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 ns3.beebytecdn.com

Showing DNS history for 2026-08-26 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-26 12:42 639233445367152284
26 ms 69.168.230.171
37 2026-08-26 12:24 639233434974187439
63 ms 69.168.230.171
36 2026-08-26 12:07 639233424567558554
30 ms 69.168.230.171
35 2026-08-26 11:49 639233414056832719
84 ms 69.168.230.171
34 2026-08-26 11:32 639233403515141099
83 ms 69.168.230.171
33 2026-08-26 10:37 639233370841350248
15 ms 69.168.230.171
32 2026-08-26 10:20 639233360361507238
2026 ms 69.168.230.171
31 2026-08-26 10:03 639233350067824371
221 ms 69.168.230.171
30 2026-08-26 09:45 639233339545274518
278 ms 69.168.230.171
29 2026-08-26 09:28 639233329214918079
37 ms 69.168.230.171
28 2026-08-26 09:11 639233318749762337
33 ms 69.168.230.171
27 2026-08-26 08:53 639233308387917838
50 ms 69.168.230.171
26 2026-08-26 08:36 639233297961740122
7 ms 69.168.230.171
25 2026-08-26 08:19 639233287487159094
38 ms 69.168.230.171
24 2026-08-26 08:01 639233276995531707
2024 ms 69.168.230.171
23 2026-08-26 07:44 639233266521568229
39 ms 69.168.230.171
22 2026-08-26 07:26 639233256081047431
59 ms 69.168.230.171
21 2026-08-26 06:32 639233223620132921
19 ms 69.168.230.171
20 2026-08-26 06:15 639233213287814244
2032 ms 69.168.230.171
19 2026-08-26 05:58 639233202925983161
58 ms 69.168.230.171
18 2026-08-26 05:40 639233192644780696
28 ms 69.168.230.171
17 2026-08-26 05:23 639233182401183833
38 ms 69.168.230.171
16 2026-08-26 05:06 639233172074181051
83 ms 69.168.230.171
15 2026-08-26 04:49 639233161808421455
41 ms 69.168.230.171
14 2026-08-26 04:32 639233151357344052
2256 ms 69.168.230.171
13 2026-08-26 04:14 639233141034116946
65 ms 69.168.230.171
12 2026-08-26 03:57 639233130828334142
36 ms 69.168.230.171
11 2026-08-26 03:40 639233120373450007
69 ms 69.168.230.171
10 2026-08-26 03:23 639233110066216193
2034 ms 69.168.230.171
9 2026-08-26 02:29 639233078065410564
73 ms 69.168.230.171
8 2026-08-26 02:12 639233067787457832
7 ms 69.168.230.171
7 2026-08-26 01:55 639233057501801162
72 ms 69.168.230.171
6 2026-08-26 01:38 639233047089431703
62 ms 69.168.230.171
5 2026-08-26 01:21 639233036754790688
12 ms 69.168.230.171
4 2026-08-26 01:03 639233026412602472
7 ms 69.168.230.171
3 2026-08-26 00:46 639233016064066127
85 ms 69.168.230.171
2 2026-08-26 00:29 639233005922655772
29 ms 69.168.230.171
1 2026-08-26 00:12 639232995672256907
36 ms 69.168.230.171