DNS response history for dns1.nodeeps.de

dns1.nodeeps.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 260 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 dns1.nodeeps.de.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

260 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

84.38.79.93

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