DNS response history for ns1.resdomain.net

ns1.resdomain.net 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 37 DNS check records, 35 successful responses, 2 failed responses, and 314 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.resdomain.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

314 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

146.59.156.110

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.resdomain.net

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