DNS response history for ns5.mincharme.eu

ns5.mincharme.eu 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 28 DNS check records, 28 successful responses, 0 failed responses, and 340 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.mincharme.eu.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

340 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.89.212.232

Most recently resolved hosting IP on selected date

Successful Responses

28

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.mincharme.eu

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
28 2026-08-25 09:39 639232471861770303
27 ms 51.89.212.232
27 2026-08-25 09:22 639232461630217327
27 ms 51.89.212.232
26 2026-08-25 09:05 639232451282965990
11 ms 51.89.212.232
25 2026-08-25 08:47 639232440814614938
69 ms 51.89.212.232
24 2026-08-25 08:30 639232430410720425
202 ms 51.89.212.232
23 2026-08-25 08:13 639232420003096185
25 ms 51.89.212.232
22 2026-08-25 07:55 639232409467287444
46 ms 51.89.212.232
21 2026-08-25 07:38 639232399077195997
2043 ms 51.89.212.232
20 2026-08-25 07:21 639232388731528337
2027 ms 51.89.212.232
19 2026-08-25 07:03 639232378288598612
55 ms 51.89.212.232
18 2026-08-25 06:10 639232346196373643
31 ms 51.89.212.232
17 2026-08-25 05:53 639232336112370741
2066 ms 51.89.212.232
16 2026-08-25 05:36 639232326146508970
47 ms 51.89.212.232
15 2026-08-25 05:20 639232316189381720
77 ms 51.89.212.232
14 2026-08-25 05:03 639232306217998913
59 ms 51.89.212.232
13 2026-08-25 04:46 639232296255744174
2026 ms 51.89.212.232
12 2026-08-25 04:30 639232286095760789
25 ms 51.89.212.232
11 2026-08-25 04:13 639232276086186273
22 ms 51.89.212.232
10 2026-08-25 03:56 639232265900986425
48 ms 51.89.212.232
9 2026-08-25 03:39 639232255723518075
127 ms 51.89.212.232
8 2026-08-25 03:22 639232245484452890
26 ms 51.89.212.232
7 2026-08-25 03:05 639232235157175331
134 ms 51.89.212.232
6 2026-08-25 02:11 639232203197189095
99 ms 51.89.212.232
5 2026-08-25 01:54 639232192844564298
30 ms 51.89.212.232
4 2026-08-25 01:37 639232182496008942
61 ms 51.89.212.232
3 2026-08-25 01:20 639232172197053132
35 ms 51.89.212.232
2 2026-08-25 00:26 639232140250307418
44 ms 51.89.212.232
1 2026-08-25 00:09 639232129927860324
27 ms 51.89.212.232