DNS response history for ns1.bebeddy.com

ns1.bebeddy.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, 27 successful responses, 0 failed responses, and 614 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.bebeddy.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

614 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.134.78.139

Most recently resolved hosting IP on selected date

Successful Responses

27

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.bebeddy.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:22 639232461630217327
42 ms 91.134.78.139
26 2026-08-25 09:05 639232451282965990
59 ms 91.134.78.139
25 2026-08-25 08:47 639232440814614938
61 ms 91.134.78.139
24 2026-08-25 08:30 639232430410720425
7 ms 91.134.78.139
23 2026-08-25 08:13 639232420003096185
16 ms 91.134.78.139
22 2026-08-25 07:55 639232409467287444
1640 ms 91.134.78.139
21 2026-08-25 07:38 639232399077195997
54 ms 91.134.78.139
20 2026-08-25 07:21 639232388731528337
2059 ms 91.134.78.139
19 2026-08-25 07:03 639232378288598612
94 ms 91.134.78.139
18 2026-08-25 06:10 639232346196373643
2198 ms 91.134.78.139
17 2026-08-25 05:53 639232336112370741
2021 ms 91.134.78.139
16 2026-08-25 05:36 639232326146508970
52 ms 91.134.78.139
15 2026-08-25 05:20 639232316189381720
66 ms 91.134.78.139
14 2026-08-25 05:03 639232306217998913
33 ms 91.134.78.139
13 2026-08-25 04:47 639232296255744174
58 ms 91.134.78.139
12 2026-08-25 04:30 639232286095760789
44 ms 91.134.78.139
11 2026-08-25 04:13 639232276086186273
1515 ms 91.134.78.139
10 2026-08-25 03:56 639232265900986425
66 ms 91.134.78.139
9 2026-08-25 03:39 639232255723518075
126 ms 91.134.78.139
8 2026-08-25 03:22 639232245484452890
27 ms 91.134.78.139
7 2026-08-25 03:05 639232235157175331
65 ms 91.134.78.139
6 2026-08-25 02:11 639232203197189095
54 ms 91.134.78.139
5 2026-08-25 01:54 639232192844564298
2008 ms 91.134.78.139
4 2026-08-25 01:37 639232182496008942
2075 ms 91.134.78.139
3 2026-08-25 01:20 639232172197053132
49 ms 91.134.78.139
2 2026-08-25 00:26 639232140250307418
46 ms 91.134.78.139
1 2026-08-25 00:09 639232129927860324
2037 ms 91.134.78.139