DNS response history for ns-1.q-leap.de

ns-1.q-leap.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 35 DNS check records, 34 successful responses, 1 failed responses, and 688 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 ns-1.q-leap.de.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

688 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.120.173.37

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns-1.q-leap.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
35 2026-08-27 11:08 639234253963286387
25 ms 37.120.173.37
34 2026-08-27 10:51 639234243654907465
28 ms 37.120.173.37
33 2026-08-27 10:34 639234233269654413
2033 ms 37.120.173.37
32 2026-08-27 10:16 639234222943951923
49 ms 37.120.173.37
31 2026-08-27 09:59 639234212558002823
46 ms 37.120.173.37
30 2026-08-27 09:42 639234202117531850
84 ms 37.120.173.37
29 2026-08-27 09:24 639234191649612722
2016 ms 37.120.173.37
28 2026-08-27 09:07 639234181105879568
4044 ms 37.120.173.37
27 2026-08-27 08:49 639234170713214496
2041 ms 37.120.173.37
26 2026-08-27 08:32 639234160341037652
28 ms 37.120.173.37
25 2026-08-27 08:15 639234149799404224
2025 ms 37.120.173.37
24 2026-08-27 07:57 639234139553286469
31 ms 37.120.173.37
23 2026-08-27 07:04 639234107183588293
34 ms 37.120.173.37
22 2026-08-27 06:46 639234096905435724
41 ms 37.120.173.37
21 2026-08-27 06:29 639234086579410775
22 ms 37.120.173.37
20 2026-08-27 06:12 639234076291157956
51 ms 37.120.173.37
19 2026-08-27 05:55 639234065981939454
-
18 2026-08-27 05:38 639234055548642997
38 ms 37.120.173.37
17 2026-08-27 05:20 639234045267979603
2045 ms 37.120.173.37
16 2026-08-27 05:03 639234034999717463
13 ms 37.120.173.37
15 2026-08-27 04:46 639234024739225358
44 ms 37.120.173.37
14 2026-08-27 04:29 639234014311170162
62 ms 37.120.173.37
13 2026-08-27 04:11 639234003806017640
65 ms 37.120.173.37
12 2026-08-27 03:54 639233993356203030
36 ms 37.120.173.37
11 2026-08-27 03:00 639233961301716608
46 ms 37.120.173.37
10 2026-08-27 02:43 639233950834200647
22 ms 37.120.173.37
9 2026-08-27 02:26 639233940431849026
2064 ms 37.120.173.37
8 2026-08-27 02:08 639233930110596398
16 ms 37.120.173.37
7 2026-08-27 01:51 639233919705434540
42 ms 37.120.173.37
6 2026-08-27 01:34 639233909452807845
79 ms 37.120.173.37
5 2026-08-27 01:17 639233899096420820
2048 ms 37.120.173.37
4 2026-08-27 00:59 639233888707824939
73 ms 37.120.173.37
3 2026-08-27 00:42 639233878461203802
2044 ms 37.120.173.37
2 2026-08-27 00:25 639233868060868209
2049 ms 37.120.173.37
1 2026-08-27 00:07 639233857450922991
11 ms 37.120.173.37