DNS response history for a.ns.bezdekov.net

a.ns.bezdekov.net 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-27. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 450 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 a.ns.bezdekov.net.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

450 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

77.104.222.110

Most recently resolved hosting IP on selected date

Successful Responses

26

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 a.ns.bezdekov.net

Showing DNS history for 2026-08-27 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
26 2026-08-27 08:33 639234160341037652
455 ms 77.104.222.110
25 2026-08-27 08:16 639234149799404224
58 ms 77.104.222.110
24 2026-08-27 07:59 639234139553286469
61 ms 77.104.222.110
23 2026-08-27 07:05 639234107183588293
62 ms 77.104.222.110
22 2026-08-27 06:48 639234096905435724
2031 ms 77.104.222.110
21 2026-08-27 06:31 639234086579410775
69 ms 77.104.222.110
20 2026-08-27 06:14 639234076291157956
2048 ms 77.104.222.110
19 2026-08-27 05:56 639234065981939454
71 ms 77.104.222.110
18 2026-08-27 05:39 639234055548642997
69 ms 77.104.222.110
17 2026-08-27 05:22 639234045267979603
38 ms 77.104.222.110
16 2026-08-27 05:05 639234034999717463
72 ms 77.104.222.110
15 2026-08-27 04:48 639234024739225358
2008 ms 77.104.222.110
14 2026-08-27 04:30 639234014311170162
64 ms 77.104.222.110
13 2026-08-27 04:13 639234003806017640
72 ms 77.104.222.110
12 2026-08-27 03:55 639233993356203030
16 ms 77.104.222.110
11 2026-08-27 03:02 639233961301716608
2069 ms 77.104.222.110
10 2026-08-27 02:45 639233950834200647
9 ms 77.104.222.110
9 2026-08-27 02:27 639233940431849026
71 ms 77.104.222.110
8 2026-08-27 02:10 639233930110596398
53 ms 77.104.222.110
7 2026-08-27 01:53 639233919705434540
62 ms 77.104.222.110
6 2026-08-27 01:36 639233909452807845
64 ms 77.104.222.110
5 2026-08-27 01:18 639233899096420820
61 ms 77.104.222.110
4 2026-08-27 01:01 639233888707824939
73 ms 77.104.222.110
3 2026-08-27 00:44 639233878461203802
2020 ms 77.104.222.110
2 2026-08-27 00:26 639233868060868209
24 ms 77.104.222.110
1 2026-08-27 00:09 639233857450922991
10 ms 77.104.222.110