DNS response history for ns1.rich.com

ns1.rich.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 36 DNS check records, 36 successful responses, 0 failed responses, and 235 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.rich.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

235 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.129.32.68

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.rich.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
36 2026-08-25 12:38 639232576780683689
2162 ms 52.129.32.68
35 2026-08-25 12:21 639232566381512620
122 ms 52.129.32.68
34 2026-08-25 12:03 639232556111768563
126 ms 52.129.32.68
33 2026-08-25 11:46 639232545839529039
90 ms 52.129.32.68
32 2026-08-25 11:29 639232535349285207
124 ms 52.129.32.68
31 2026-08-25 11:12 639232524938080723
282 ms 52.129.32.68
30 2026-08-25 10:18 639232492740373468
281 ms 52.129.32.68
29 2026-08-25 10:01 639232482235303141
99 ms 52.129.32.68
28 2026-08-25 09:43 639232471861770303
120 ms 52.129.32.68
27 2026-08-25 09:26 639232461630217327
281 ms 52.129.32.68
26 2026-08-25 09:09 639232451282965990
318 ms 52.129.32.68
25 2026-08-25 08:51 639232440814614938
121 ms 52.129.32.68
24 2026-08-25 08:34 639232430410720425
125 ms 52.129.32.68
23 2026-08-25 08:17 639232420003096185
99 ms 52.129.32.68
22 2026-08-25 07:59 639232409467287444
279 ms 52.129.32.68
21 2026-08-25 07:42 639232399077195997
123 ms 52.129.32.68
20 2026-08-25 07:25 639232388731528337
123 ms 52.129.32.68
19 2026-08-25 07:07 639232378288598612
282 ms 52.129.32.68
18 2026-08-25 06:14 639232346196373643
276 ms 52.129.32.68
17 2026-08-25 05:57 639232336112370741
129 ms 52.129.32.68
16 2026-08-25 05:40 639232326146508970
281 ms 52.129.32.68
15 2026-08-25 05:23 639232316189381720
285 ms 52.129.32.68
14 2026-08-25 05:07 639232306217998913
278 ms 52.129.32.68
13 2026-08-25 04:50 639232296255744174
142 ms 52.129.32.68
12 2026-08-25 04:33 639232286095760789
119 ms 52.129.32.68
11 2026-08-25 04:16 639232276086186273
279 ms 52.129.32.68
10 2026-08-25 04:00 639232265900986425
122 ms 52.129.32.68
9 2026-08-25 03:43 639232255723518075
118 ms 52.129.32.68
8 2026-08-25 03:26 639232245484452890
112 ms 52.129.32.68
7 2026-08-25 03:09 639232235157175331
145 ms 52.129.32.68
6 2026-08-25 02:15 639232203197189095
117 ms 52.129.32.68
5 2026-08-25 01:58 639232192844564298
119 ms 52.129.32.68
4 2026-08-25 01:41 639232182496008942
119 ms 52.129.32.68
3 2026-08-25 01:24 639232172197053132
276 ms 52.129.32.68
2 2026-08-25 00:30 639232140250307418
121 ms 52.129.32.68
1 2026-08-25 00:13 639232129927860324
271 ms 52.129.32.68