DNS response history for ns1.resolver.cx

ns1.resolver.cx 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 35 DNS check records, 35 successful responses, 0 failed responses, and 503 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.resolver.cx.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

503 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.96.165

Most recently resolved hosting IP on selected date

Successful Responses

35

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.resolver.cx

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
35 2026-08-25 12:12 639232566381512620
2019 ms 185.136.96.165
34 2026-08-25 11:55 639232556111768563
32 ms 185.136.96.165
33 2026-08-25 11:37 639232545839529039
55 ms 185.136.96.165
32 2026-08-25 11:20 639232535349285207
41 ms 185.136.96.165
31 2026-08-25 11:03 639232524938080723
8 ms 185.136.96.165
30 2026-08-25 10:09 639232492740373468
6 ms 185.136.96.165
29 2026-08-25 09:52 639232482235303141
14 ms 185.136.96.165
28 2026-08-25 09:34 639232471861770303
2039 ms 185.136.96.165
27 2026-08-25 09:17 639232461630217327
16 ms 185.136.96.165
26 2026-08-25 09:00 639232451282965990
38 ms 185.136.96.165
25 2026-08-25 08:42 639232440814614938
32 ms 185.136.96.165
24 2026-08-25 08:25 639232430410720425
15 ms 185.136.96.165
23 2026-08-25 08:08 639232420003096185
5 ms 185.136.96.165
22 2026-08-25 07:50 639232409467287444
2069 ms 185.136.96.165
21 2026-08-25 07:33 639232399077195997
7 ms 185.136.96.165
20 2026-08-25 07:16 639232388731528337
15 ms 185.136.96.165
19 2026-08-25 06:58 639232378288598612
775 ms 185.136.96.165
18 2026-08-25 06:05 639232346196373643
4 ms 185.136.96.165
17 2026-08-25 05:48 639232336112370741
40 ms 185.136.96.165
16 2026-08-25 05:31 639232326146508970
19 ms 185.136.96.165
15 2026-08-25 05:15 639232316189381720
14 ms 185.136.96.165
14 2026-08-25 04:58 639232306217998913
2018 ms 185.136.96.165
13 2026-08-25 04:42 639232296255744174
5 ms 185.136.96.165
12 2026-08-25 04:25 639232286095760789
5 ms 185.136.96.165
11 2026-08-25 04:08 639232276086186273
7 ms 185.136.96.165
10 2026-08-25 03:51 639232265900986425
2043 ms 185.136.96.165
9 2026-08-25 03:34 639232255723518075
6 ms 185.136.96.165
8 2026-08-25 03:17 639232245484452890
21 ms 185.136.96.165
7 2026-08-25 03:00 639232235157175331
2066 ms 185.136.96.165
6 2026-08-25 02:06 639232203197189095
7 ms 185.136.96.165
5 2026-08-25 01:49 639232192844564298
5 ms 185.136.96.165
4 2026-08-25 01:32 639232182496008942
2050 ms 185.136.96.165
3 2026-08-25 01:15 639232172197053132
8 ms 185.136.96.165
2 2026-08-25 00:21 639232140250307418
12 ms 185.136.96.165
1 2026-08-25 00:04 639232129927860324
2079 ms 185.136.96.165