DNS response history for ns1.daybeam.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

420 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.56.24.165

Most recently resolved hosting IP on selected date

Successful Responses

34

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.daybeam.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
34 2026-08-26 11:34 639233403515141099
219 ms 149.56.24.165
33 2026-08-26 10:39 639233370841350248
219 ms 149.56.24.165
32 2026-08-26 10:22 639233360361507238
104 ms 149.56.24.165
31 2026-08-26 10:05 639233350067824371
240 ms 149.56.24.165
30 2026-08-26 09:48 639233339545274518
157 ms 149.56.24.165
29 2026-08-26 09:30 639233329214918079
223 ms 149.56.24.165
28 2026-08-26 09:13 639233318749762337
2034 ms 149.56.24.165
27 2026-08-26 08:56 639233308387917838
218 ms 149.56.24.165
26 2026-08-26 08:38 639233297961740122
217 ms 149.56.24.165
25 2026-08-26 08:21 639233287487159094
213 ms 149.56.24.165
24 2026-08-26 08:03 639233276995531707
221 ms 149.56.24.165
23 2026-08-26 07:46 639233266521568229
245 ms 149.56.24.165
22 2026-08-26 07:28 639233256081047431
219 ms 149.56.24.165
21 2026-08-26 06:34 639233223620132921
226 ms 149.56.24.165
20 2026-08-26 06:17 639233213287814244
9 ms 149.56.24.165
19 2026-08-26 06:00 639233202925983161
231 ms 149.56.24.165
18 2026-08-26 05:43 639233192644780696
2115 ms 149.56.24.165
17 2026-08-26 05:25 639233182401183833
237 ms 149.56.24.165
16 2026-08-26 05:08 639233172074181051
10 ms 149.56.24.165
15 2026-08-26 04:51 639233161808421455
226 ms 149.56.24.165
14 2026-08-26 04:34 639233151357344052
229 ms 149.56.24.165
13 2026-08-26 04:17 639233141034116946
219 ms 149.56.24.165
12 2026-08-26 04:00 639233130828334142
221 ms 149.56.24.165
11 2026-08-26 03:42 639233120373450007
219 ms 149.56.24.165
10 2026-08-26 03:25 639233110066216193
124 ms 149.56.24.165
9 2026-08-26 02:32 639233078065410564
217 ms 149.56.24.165
8 2026-08-26 02:14 639233067787457832
219 ms 149.56.24.165
7 2026-08-26 01:57 639233057501801162
240 ms 149.56.24.165
6 2026-08-26 01:40 639233047089431703
219 ms 149.56.24.165
5 2026-08-26 01:23 639233036754790688
221 ms 149.56.24.165
4 2026-08-26 01:06 639233026412602472
2125 ms 149.56.24.165
3 2026-08-26 00:48 639233016064066127
2106 ms 149.56.24.165
2 2026-08-26 00:31 639233005922655772
219 ms 149.56.24.165
1 2026-08-26 00:14 639232995672256907
112 ms 149.56.24.165