DNS response history for ns5.nop.berlin

ns5.nop.berlin 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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 180 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 ns5.nop.berlin.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

180 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.109.78.171

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns5.nop.berlin

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:15 639232492740373468
37 ms 65.109.78.171
29 2026-08-25 09:58 639232482235303141
24 ms 65.109.78.171
28 2026-08-25 09:40 639232471861770303
45 ms 65.109.78.171
27 2026-08-25 09:23 639232461630217327
47 ms 65.109.78.171
26 2026-08-25 09:06 639232451282965990
271 ms 65.109.78.171
25 2026-08-25 08:48 639232440814614938
25 ms 65.109.78.171
24 2026-08-25 08:31 639232430410720425
48 ms 65.109.78.171
23 2026-08-25 08:14 639232420003096185
32 ms 65.109.78.171
22 2026-08-25 07:56 639232409467287444
40 ms 65.109.78.171
21 2026-08-25 07:39 639232399077195997
36 ms 65.109.78.171
20 2026-08-25 07:22 639232388731528337
30 ms 65.109.78.171
19 2026-08-25 07:04 639232378288598612
39 ms 65.109.78.171
18 2026-08-25 06:11 639232346196373643
26 ms 65.109.78.171
17 2026-08-25 05:54 639232336112370741
2026 ms 65.109.78.171
16 2026-08-25 05:37 639232326146508970
30 ms 65.109.78.171
15 2026-08-25 05:21 639232316189381720
15 ms 65.109.78.171
14 2026-08-25 05:04 639232306217998913
39 ms 65.109.78.171
13 2026-08-25 04:48 639232296255744174
26 ms 65.109.78.171
12 2026-08-25 04:31 639232286095760789
15 ms 65.109.78.171
11 2026-08-25 04:14 639232276086186273
41 ms 65.109.78.171
10 2026-08-25 03:57 639232265900986425
42 ms 65.109.78.171
9 2026-08-25 03:40 639232255723518075
10 ms 65.109.78.171
8 2026-08-25 03:23 639232245484452890
39 ms 65.109.78.171
7 2026-08-25 03:06 639232235157175331
12 ms 65.109.78.171
6 2026-08-25 02:12 639232203197189095
22 ms 65.109.78.171
5 2026-08-25 01:55 639232192844564298
12 ms 65.109.78.171
4 2026-08-25 01:38 639232182496008942
8 ms 65.109.78.171
3 2026-08-25 01:21 639232172197053132
141 ms 65.109.78.171
2 2026-08-25 00:27 639232140250307418
99 ms 65.109.78.171
1 2026-08-25 00:10 639232129927860324
2121 ms 65.109.78.171