DNS response history for ns4.nimerik.com

ns4.nimerik.com 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, 28 successful responses, 2 failed responses, and 254 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 ns4.nimerik.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

254 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.206.180.169

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

7%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns4.nimerik.com

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:12 639232492740373468
34 ms 185.206.180.169
29 2026-08-25 09:54 639232482235303141
178 ms 185.206.180.169
28 2026-08-25 09:37 639232471861770303
2041 ms 185.206.180.169
27 2026-08-25 09:20 639232461630217327
10 ms 185.206.180.169
26 2026-08-25 09:03 639232451282965990
2031 ms 185.206.180.169
25 2026-08-25 08:45 639232440814614938
-
24 2026-08-25 08:28 639232430410720425
20 ms 185.206.180.169
23 2026-08-25 08:11 639232420003096185
43 ms 185.206.180.169
22 2026-08-25 07:53 639232409467287444
104 ms 185.206.180.169
21 2026-08-25 07:36 639232399077195997
7 ms 185.206.180.169
20 2026-08-25 07:19 639232388731528337
-
19 2026-08-25 07:01 639232378288598612
12 ms 185.206.180.169
18 2026-08-25 06:07 639232346196373643
11 ms 185.206.180.169
17 2026-08-25 05:51 639232336112370741
100 ms 185.206.180.169
16 2026-08-25 05:34 639232326146508970
111 ms 185.206.180.169
15 2026-08-25 05:17 639232316189381720
25 ms 185.206.180.169
14 2026-08-25 05:01 639232306217998913
24 ms 185.206.180.169
13 2026-08-25 04:44 639232296255744174
25 ms 185.206.180.169
12 2026-08-25 04:27 639232286095760789
6 ms 185.206.180.169
11 2026-08-25 04:11 639232276086186273
39 ms 185.206.180.169
10 2026-08-25 03:54 639232265900986425
37 ms 185.206.180.169
9 2026-08-25 03:37 639232255723518075
41 ms 185.206.180.169
8 2026-08-25 03:20 639232245484452890
8 ms 185.206.180.169
7 2026-08-25 03:02 639232235157175331
12 ms 185.206.180.169
6 2026-08-25 02:09 639232203197189095
98 ms 185.206.180.169
5 2026-08-25 01:52 639232192844564298
9 ms 185.206.180.169
4 2026-08-25 01:35 639232182496008942
7 ms 185.206.180.169
3 2026-08-25 01:17 639232172197053132
46 ms 185.206.180.169
2 2026-08-25 00:24 639232140250307418
2021 ms 185.206.180.169
1 2026-08-25 00:07 639232129927860324
9 ms 185.206.180.169