DNS response history for ns2.nesebar-lan.net

ns2.nesebar-lan.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 27 DNS check records, 27 successful responses, 0 failed responses, and 140 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 ns2.nesebar-lan.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

140 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.160.18.210

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 ns2.nesebar-lan.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
27 2026-08-27 08:51 639234170713214496
81 ms 109.160.18.210
26 2026-08-27 08:34 639234160341037652
66 ms 109.160.18.210
25 2026-08-27 08:17 639234149799404224
37 ms 109.160.18.210
24 2026-08-27 08:00 639234139553286469
43 ms 109.160.18.210
23 2026-08-27 07:06 639234107183588293
88 ms 109.160.18.210
22 2026-08-27 06:49 639234096905435724
86 ms 109.160.18.210
21 2026-08-27 06:31 639234086579410775
59 ms 109.160.18.210
20 2026-08-27 06:14 639234076291157956
44 ms 109.160.18.210
19 2026-08-27 05:57 639234065981939454
85 ms 109.160.18.210
18 2026-08-27 05:40 639234055548642997
2189 ms 109.160.18.210
17 2026-08-27 05:22 639234045267979603
74 ms 109.160.18.210
16 2026-08-27 05:05 639234034999717463
65 ms 109.160.18.210
15 2026-08-27 04:48 639234024739225358
37 ms 109.160.18.210
14 2026-08-27 04:31 639234014311170162
38 ms 109.160.18.210
13 2026-08-27 04:13 639234003806017640
122 ms 109.160.18.210
12 2026-08-27 03:56 639233993356203030
62 ms 109.160.18.210
11 2026-08-27 03:03 639233961301716608
76 ms 109.160.18.210
10 2026-08-27 02:45 639233950834200647
89 ms 109.160.18.210
9 2026-08-27 02:28 639233940431849026
38 ms 109.160.18.210
8 2026-08-27 02:11 639233930110596398
86 ms 109.160.18.210
7 2026-08-27 01:53 639233919705434540
64 ms 109.160.18.210
6 2026-08-27 01:36 639233909452807845
37 ms 109.160.18.210
5 2026-08-27 01:19 639233899096420820
9 ms 109.160.18.210
4 2026-08-27 01:02 639233888707824939
36 ms 109.160.18.210
3 2026-08-27 00:44 639233878461203802
34 ms 109.160.18.210
2 2026-08-27 00:27 639233868060868209
44 ms 109.160.18.210
1 2026-08-27 00:10 639233857450922991
97 ms 109.160.18.210