DNS response history for ns2.server.envago.de

ns2.server.envago.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, 35 successful responses, 0 failed responses, and 397 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.server.envago.de.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

397 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.47.230.135

Most recently resolved hosting IP on selected date

Successful Responses

35

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.server.envago.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:07 639234253963286387
2024 ms 78.47.230.135
34 2026-08-27 10:50 639234243654907465
47 ms 78.47.230.135
33 2026-08-27 10:33 639234233269654413
44 ms 78.47.230.135
32 2026-08-27 10:15 639234222943951923
87 ms 78.47.230.135
31 2026-08-27 09:58 639234212558002823
55 ms 78.47.230.135
30 2026-08-27 09:41 639234202117531850
56 ms 78.47.230.135
29 2026-08-27 09:23 639234191649612722
43 ms 78.47.230.135
28 2026-08-27 09:06 639234181105879568
27 ms 78.47.230.135
27 2026-08-27 08:48 639234170713214496
91 ms 78.47.230.135
26 2026-08-27 08:31 639234160341037652
55 ms 78.47.230.135
25 2026-08-27 08:14 639234149799404224
34 ms 78.47.230.135
24 2026-08-27 07:57 639234139553286469
58 ms 78.47.230.135
23 2026-08-27 07:03 639234107183588293
39 ms 78.47.230.135
22 2026-08-27 06:45 639234096905435724
98 ms 78.47.230.135
21 2026-08-27 06:28 639234086579410775
5 ms 78.47.230.135
20 2026-08-27 06:11 639234076291157956
39 ms 78.47.230.135
19 2026-08-27 05:54 639234065981939454
86 ms 78.47.230.135
18 2026-08-27 05:37 639234055548642997
30 ms 78.47.230.135
17 2026-08-27 05:19 639234045267979603
84 ms 78.47.230.135
16 2026-08-27 05:02 639234034999717463
96 ms 78.47.230.135
15 2026-08-27 04:45 639234024739225358
71 ms 78.47.230.135
14 2026-08-27 04:28 639234014311170162
58 ms 78.47.230.135
13 2026-08-27 04:10 639234003806017640
67 ms 78.47.230.135
12 2026-08-27 03:53 639233993356203030
4085 ms 78.47.230.135
11 2026-08-27 02:59 639233961301716608
2038 ms 78.47.230.135
10 2026-08-27 02:42 639233950834200647
2013 ms 78.47.230.135
9 2026-08-27 02:25 639233940431849026
68 ms 78.47.230.135
8 2026-08-27 02:07 639233930110596398
33 ms 78.47.230.135
7 2026-08-27 01:50 639233919705434540
10 ms 78.47.230.135
6 2026-08-27 01:33 639233909452807845
2067 ms 78.47.230.135
5 2026-08-27 01:16 639233899096420820
69 ms 78.47.230.135
4 2026-08-27 00:58 639233888707824939
27 ms 78.47.230.135
3 2026-08-27 00:41 639233878461203802
48 ms 78.47.230.135
2 2026-08-27 00:24 639233868060868209
73 ms 78.47.230.135
1 2026-08-27 00:06 639233857450922991
68 ms 78.47.230.135