DNS response history for ns1.beemacover.com

ns1.beemacover.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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 219 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.beemacover.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

219 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.145.50.247

Most recently resolved hosting IP on selected date

Successful Responses

31

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.beemacover.com

Showing DNS history for 2026-08-25 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
31 2026-08-25 10:22 639232492740373468
3 ms 103.145.50.247
30 2026-08-25 10:05 639232482235303141
277 ms 103.145.50.247
29 2026-08-25 09:48 639232471861770303
279 ms 103.145.50.247
28 2026-08-25 09:31 639232461630217327
269 ms 103.145.50.247
27 2026-08-25 09:13 639232451282965990
278 ms 103.145.50.247
26 2026-08-25 08:56 639232440814614938
277 ms 103.145.50.247
25 2026-08-25 08:39 639232430410720425
270 ms 103.145.50.247
24 2026-08-25 08:21 639232420003096185
12 ms 103.145.50.247
23 2026-08-25 08:04 639232409467287444
277 ms 103.145.50.247
22 2026-08-25 07:47 639232399077195997
280 ms 103.145.50.247
21 2026-08-25 07:29 639232388731528337
269 ms 103.145.50.247
20 2026-08-25 07:12 639232378288598612
4 ms 103.145.50.247
19 2026-08-25 06:18 639232346196373643
4 ms 103.145.50.247
18 2026-08-25 06:01 639232336112370741
273 ms 103.145.50.247
17 2026-08-25 05:44 639232326146508970
1206 ms 103.145.50.247
16 2026-08-25 05:28 639232316189381720
279 ms 103.145.50.247
15 2026-08-25 05:11 639232306217998913
3 ms 103.145.50.247
14 2026-08-25 04:55 639232296255744174
274 ms 103.145.50.247
13 2026-08-25 04:38 639232286095760789
3 ms 103.145.50.247
12 2026-08-25 04:21 639232276086186273
263 ms 103.145.50.247
11 2026-08-25 04:04 639232265900986425
266 ms 103.145.50.247
10 2026-08-25 03:47 639232255723518075
2 ms 103.145.50.247
9 2026-08-25 03:30 639232245484452890
283 ms 103.145.50.247
8 2026-08-25 03:13 639232235157175331
303 ms 103.145.50.247
7 2026-08-25 02:20 639232203197189095
4 ms 103.145.50.247
6 2026-08-25 02:03 639232192844564298
2 ms 103.145.50.247
5 2026-08-25 01:45 639232182496008942
303 ms 103.145.50.247
4 2026-08-25 01:28 639232172197053132
272 ms 103.145.50.247
3 2026-08-25 00:35 639232140250307418
270 ms 103.145.50.247
2 2026-08-25 00:18 639232129927860324
273 ms 103.145.50.247
1 2026-08-25 00:01 639232119551972438
7 ms 103.145.50.247