DNS response history for ns2phi.passiv.de

ns2phi.passiv.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 36 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 ns2phi.passiv.de.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

36 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.86.192.122

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2phi.passiv.de

Showing DNS history for 2026-08-26 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
34 2026-08-26 11:31 639233403515141099
36 ms 217.86.192.122
33 2026-08-26 10:36 639233370841350248
15 ms 217.86.192.122
32 2026-08-26 10:19 639233360361507238
38 ms 217.86.192.122
31 2026-08-26 10:02 639233350067824371
80 ms 217.86.192.122
30 2026-08-26 09:44 639233339545274518
22 ms 217.86.192.122
29 2026-08-26 09:27 639233329214918079
11 ms 217.86.192.122
28 2026-08-26 09:09 639233318749762337
45 ms 217.86.192.122
27 2026-08-26 08:52 639233308387917838
31 ms 217.86.192.122
26 2026-08-26 08:35 639233297961740122
85 ms 217.86.192.122
25 2026-08-26 08:17 639233287487159094
40 ms 217.86.192.122
24 2026-08-26 08:00 639233276995531707
25 ms 217.86.192.122
23 2026-08-26 07:42 639233266521568229
33 ms 217.86.192.122
22 2026-08-26 07:25 639233256081047431
46 ms 217.86.192.122
21 2026-08-26 06:31 639233223620132921
34 ms 217.86.192.122
20 2026-08-26 06:14 639233213287814244
17 ms 217.86.192.122
19 2026-08-26 05:56 639233202925983161
24 ms 217.86.192.122
18 2026-08-26 05:39 639233192644780696
61 ms 217.86.192.122
17 2026-08-26 05:22 639233182401183833
59 ms 217.86.192.122
16 2026-08-26 05:05 639233172074181051
33 ms 217.86.192.122
15 2026-08-26 04:48 639233161808421455
50 ms 217.86.192.122
14 2026-08-26 04:30 639233151357344052
21 ms 217.86.192.122
13 2026-08-26 04:13 639233141034116946
62 ms 217.86.192.122
12 2026-08-26 03:56 639233130828334142
15 ms 217.86.192.122
11 2026-08-26 03:39 639233120373450007
13 ms 217.86.192.122
10 2026-08-26 03:21 639233110066216193
27 ms 217.86.192.122
9 2026-08-26 02:28 639233078065410564
39 ms 217.86.192.122
8 2026-08-26 02:11 639233067787457832
18 ms 217.86.192.122
7 2026-08-26 01:54 639233057501801162
49 ms 217.86.192.122
6 2026-08-26 01:37 639233047089431703
34 ms 217.86.192.122
5 2026-08-26 01:19 639233036754790688
59 ms 217.86.192.122
4 2026-08-26 01:02 639233026412602472
10 ms 217.86.192.122
3 2026-08-26 00:45 639233016064066127
18 ms 217.86.192.122
2 2026-08-26 00:28 639233005922655772
37 ms 217.86.192.122
1 2026-08-26 00:11 639232995672256907
31 ms 217.86.192.122