DNS response history for ns02.ccc-ffm.de

ns02.ccc-ffm.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-25. For this date, NameServerHistory found 29 DNS check records, 28 successful responses, 1 failed responses, and 189 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 ns02.ccc-ffm.de.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

189 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.156.255.38

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns02.ccc-ffm.de

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
29 2026-08-25 10:00 639232482235303141
419 ms 185.156.255.38
28 2026-08-25 09:42 639232471861770303
22 ms 185.156.255.38
27 2026-08-25 09:25 639232461630217327
26 ms 185.156.255.38
26 2026-08-25 09:08 639232451282965990
12 ms 185.156.255.38
25 2026-08-25 08:51 639232440814614938
2059 ms 185.156.255.38
24 2026-08-25 08:33 639232430410720425
12 ms 185.156.255.38
23 2026-08-25 08:16 639232420003096185
12 ms 185.156.255.38
22 2026-08-25 07:59 639232409467287444
428 ms 185.156.255.38
21 2026-08-25 07:41 639232399077195997
10 ms 185.156.255.38
20 2026-08-25 07:24 639232388731528337
27 ms 185.156.255.38
19 2026-08-25 07:06 639232378288598612
20 ms 185.156.255.38
18 2026-08-25 06:13 639232346196373643
-
17 2026-08-25 05:56 639232336112370741
15 ms 185.156.255.38
16 2026-08-25 05:39 639232326146508970
12 ms 185.156.255.38
15 2026-08-25 05:23 639232316189381720
18 ms 185.156.255.38
14 2026-08-25 05:06 639232306217998913
10 ms 185.156.255.38
13 2026-08-25 04:50 639232296255744174
11 ms 185.156.255.38
12 2026-08-25 04:33 639232286095760789
8 ms 185.156.255.38
11 2026-08-25 04:16 639232276086186273
9 ms 185.156.255.38
10 2026-08-25 03:59 639232265900986425
20 ms 185.156.255.38
9 2026-08-25 03:42 639232255723518075
18 ms 185.156.255.38
8 2026-08-25 03:25 639232245484452890
11 ms 185.156.255.38
7 2026-08-25 03:08 639232235157175331
12 ms 185.156.255.38
6 2026-08-25 02:15 639232203197189095
17 ms 185.156.255.38
5 2026-08-25 01:57 639232192844564298
12 ms 185.156.255.38
4 2026-08-25 01:40 639232182496008942
2020 ms 185.156.255.38
3 2026-08-25 01:23 639232172197053132
10 ms 185.156.255.38
2 2026-08-25 00:30 639232140250307418
24 ms 185.156.255.38
1 2026-08-25 00:13 639232129927860324
10 ms 185.156.255.38