DNS response history for ns1.beddyweb.com

ns1.beddyweb.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 27 DNS check records, 26 successful responses, 1 failed responses, and 345 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.beddyweb.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

345 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.134.92.150

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.beddyweb.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
27 2026-08-25 09:19 639232461630217327
48 ms 91.134.92.150
26 2026-08-25 09:02 639232451282965990
42 ms 91.134.92.150
25 2026-08-25 08:44 639232440814614938
66 ms 91.134.92.150
24 2026-08-25 08:27 639232430410720425
35 ms 91.134.92.150
23 2026-08-25 08:10 639232420003096185
121 ms 91.134.92.150
22 2026-08-25 07:52 639232409467287444
17 ms 91.134.92.150
21 2026-08-25 07:35 639232399077195997
19 ms 91.134.92.150
20 2026-08-25 07:18 639232388731528337
-
19 2026-08-25 07:00 639232378288598612
32 ms 91.134.92.150
18 2026-08-25 06:07 639232346196373643
43 ms 91.134.92.150
17 2026-08-25 05:50 639232336112370741
12 ms 91.134.92.150
16 2026-08-25 05:33 639232326146508970
16 ms 91.134.92.150
15 2026-08-25 05:17 639232316189381720
10 ms 91.134.92.150
14 2026-08-25 05:00 639232306217998913
29 ms 91.134.92.150
13 2026-08-25 04:44 639232296255744174
15 ms 91.134.92.150
12 2026-08-25 04:27 639232286095760789
44 ms 91.134.92.150
11 2026-08-25 04:10 639232276086186273
2020 ms 91.134.92.150
10 2026-08-25 03:53 639232265900986425
24 ms 91.134.92.150
9 2026-08-25 03:36 639232255723518075
31 ms 91.134.92.150
8 2026-08-25 03:19 639232245484452890
32 ms 91.134.92.150
7 2026-08-25 03:02 639232235157175331
47 ms 91.134.92.150
6 2026-08-25 02:08 639232203197189095
30 ms 91.134.92.150
5 2026-08-25 01:51 639232192844564298
2021 ms 91.134.92.150
4 2026-08-25 01:34 639232182496008942
2152 ms 91.134.92.150
3 2026-08-25 01:17 639232172197053132
19 ms 91.134.92.150
2 2026-08-25 00:24 639232140250307418
2012 ms 91.134.92.150
1 2026-08-25 00:06 639232129927860324
32 ms 91.134.92.150