DNS response history for ns1.chief-engineer.de

ns1.chief-engineer.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 36 DNS check records, 36 successful responses, 0 failed responses, and 323 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 ns1.chief-engineer.de.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

323 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.201.160.35

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns1.chief-engineer.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
36 2026-08-26 12:01 639233424567558554
63 ms 62.201.160.35
35 2026-08-26 11:44 639233414056832719
48 ms 62.201.160.35
34 2026-08-26 11:26 639233403515141099
9 ms 62.201.160.35
33 2026-08-26 10:32 639233370841350248
55 ms 62.201.160.35
32 2026-08-26 10:14 639233360361507238
40 ms 62.201.160.35
31 2026-08-26 09:57 639233350067824371
47 ms 62.201.160.35
30 2026-08-26 09:40 639233339545274518
54 ms 62.201.160.35
29 2026-08-26 09:23 639233329214918079
51 ms 62.201.160.35
28 2026-08-26 09:05 639233318749762337
35 ms 62.201.160.35
27 2026-08-26 08:48 639233308387917838
36 ms 62.201.160.35
26 2026-08-26 08:30 639233297961740122
37 ms 62.201.160.35
25 2026-08-26 08:13 639233287487159094
38 ms 62.201.160.35
24 2026-08-26 07:55 639233276995531707
43 ms 62.201.160.35
23 2026-08-26 07:38 639233266521568229
2063 ms 62.201.160.35
22 2026-08-26 07:21 639233256081047431
34 ms 62.201.160.35
21 2026-08-26 06:27 639233223620132921
4079 ms 62.201.160.35
20 2026-08-26 06:09 639233213287814244
50 ms 62.201.160.35
19 2026-08-26 05:52 639233202925983161
39 ms 62.201.160.35
18 2026-08-26 05:35 639233192644780696
32 ms 62.201.160.35
17 2026-08-26 05:18 639233182401183833
17 ms 62.201.160.35
16 2026-08-26 05:01 639233172074181051
23 ms 62.201.160.35
15 2026-08-26 04:44 639233161808421455
58 ms 62.201.160.35
14 2026-08-26 04:26 639233151357344052
34 ms 62.201.160.35
13 2026-08-26 04:09 639233141034116946
2032 ms 62.201.160.35
12 2026-08-26 03:52 639233130828334142
52 ms 62.201.160.35
11 2026-08-26 03:34 639233120373450007
91 ms 62.201.160.35
10 2026-08-26 03:17 639233110066216193
43 ms 62.201.160.35
9 2026-08-26 02:24 639233078065410564
38 ms 62.201.160.35
8 2026-08-26 02:07 639233067787457832
2049 ms 62.201.160.35
7 2026-08-26 01:50 639233057501801162
26 ms 62.201.160.35
6 2026-08-26 01:32 639233047089431703
44 ms 62.201.160.35
5 2026-08-26 01:15 639233036754790688
45 ms 62.201.160.35
4 2026-08-26 00:58 639233026412602472
66 ms 62.201.160.35
3 2026-08-26 00:41 639233016064066127
39 ms 62.201.160.35
2 2026-08-26 00:24 639233005922655772
67 ms 62.201.160.35
1 2026-08-26 00:07 639232995672256907
34 ms 62.201.160.35