DNS response history for ns2.neblis-dns.de

ns2.neblis-dns.de 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 38 DNS check records, 38 successful responses, 0 failed responses, and 504 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.neblis-dns.de.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

504 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.116.163.100

Most recently resolved hosting IP on selected date

Successful Responses

38

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.neblis-dns.de

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
38 2026-08-27 12:32 639234307007468133
22 ms 62.116.163.100
37 2026-08-27 12:15 639234296664302575
38 ms 62.116.163.100
36 2026-08-27 11:58 639234286253196126
40 ms 62.116.163.100
35 2026-08-27 11:04 639234253963286387
23 ms 62.116.163.100
34 2026-08-27 10:47 639234243654907465
53 ms 62.116.163.100
33 2026-08-27 10:29 639234233269654413
24 ms 62.116.163.100
32 2026-08-27 10:12 639234222943951923
2016 ms 62.116.163.100
31 2026-08-27 09:55 639234212558002823
2019 ms 62.116.163.100
30 2026-08-27 09:38 639234202117531850
24 ms 62.116.163.100
29 2026-08-27 09:20 639234191649612722
19 ms 62.116.163.100
28 2026-08-27 09:03 639234181105879568
36 ms 62.116.163.100
27 2026-08-27 08:45 639234170713214496
24 ms 62.116.163.100
26 2026-08-27 08:28 639234160341037652
23 ms 62.116.163.100
25 2026-08-27 08:10 639234149799404224
22 ms 62.116.163.100
24 2026-08-27 07:53 639234139553286469
30 ms 62.116.163.100
23 2026-08-27 07:00 639234107183588293
4019 ms 62.116.163.100
22 2026-08-27 06:42 639234096905435724
23 ms 62.116.163.100
21 2026-08-27 06:25 639234086579410775
37 ms 62.116.163.100
20 2026-08-27 06:08 639234076291157956
22 ms 62.116.163.100
19 2026-08-27 05:51 639234065981939454
23 ms 62.116.163.100
18 2026-08-27 05:33 639234055548642997
27 ms 62.116.163.100
17 2026-08-27 05:16 639234045267979603
4095 ms 62.116.163.100
16 2026-08-27 04:59 639234034999717463
23 ms 62.116.163.100
15 2026-08-27 04:42 639234024739225358
12 ms 62.116.163.100
14 2026-08-27 04:25 639234014311170162
25 ms 62.116.163.100
13 2026-08-27 04:07 639234003806017640
23 ms 62.116.163.100
12 2026-08-27 03:50 639233993356203030
41 ms 62.116.163.100
11 2026-08-27 02:56 639233961301716608
4042 ms 62.116.163.100
10 2026-08-27 02:39 639233950834200647
2014 ms 62.116.163.100
9 2026-08-27 02:22 639233940431849026
38 ms 62.116.163.100
8 2026-08-27 02:04 639233930110596398
42 ms 62.116.163.100
7 2026-08-27 01:47 639233919705434540
47 ms 62.116.163.100
6 2026-08-27 01:30 639233909452807845
27 ms 62.116.163.100
5 2026-08-27 01:13 639233899096420820
24 ms 62.116.163.100
4 2026-08-27 00:55 639233888707824939
39 ms 62.116.163.100
3 2026-08-27 00:38 639233878461203802
41 ms 62.116.163.100
2 2026-08-27 00:21 639233868060868209
20 ms 62.116.163.100
1 2026-08-27 00:03 639233857450922991
40 ms 62.116.163.100