DNS response history for ns2.richplan.info

ns2.richplan.info 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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 593 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 ns2.richplan.info.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

593 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.185.169.176

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns2.richplan.info

Showing DNS history for 2026-08-26 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
34 2026-08-26 11:34 639233403515141099
100 ms 192.185.169.176
33 2026-08-26 10:39 639233370841350248
205 ms 192.185.169.176
32 2026-08-26 10:22 639233360361507238
2019 ms 192.185.169.176
31 2026-08-26 10:05 639233350067824371
605 ms 192.185.169.176
30 2026-08-26 09:48 639233339545274518
103 ms 192.185.169.176
29 2026-08-26 09:30 639233329214918079
324 ms 192.185.169.176
28 2026-08-26 09:13 639233318749762337
111 ms 192.185.169.176
27 2026-08-26 08:56 639233308387917838
468 ms 192.185.169.176
26 2026-08-26 08:38 639233297961740122
829 ms 192.185.169.176
25 2026-08-26 08:21 639233287487159094
98 ms 192.185.169.176
24 2026-08-26 08:03 639233276995531707
237 ms 192.185.169.176
23 2026-08-26 07:46 639233266521568229
2015 ms 192.185.169.176
22 2026-08-26 07:28 639233256081047431
2100 ms 192.185.169.176
21 2026-08-26 06:34 639233223620132921
317 ms 192.185.169.176
20 2026-08-26 06:17 639233213287814244
7 ms 192.185.169.176
19 2026-08-26 06:00 639233202925983161
2103 ms 192.185.169.176
18 2026-08-26 05:42 639233192644780696
469 ms 192.185.169.176
17 2026-08-26 05:25 639233182401183833
1119 ms 192.185.169.176
16 2026-08-26 05:08 639233172074181051
203 ms 192.185.169.176
15 2026-08-26 04:51 639233161808421455
3 ms 192.185.169.176
14 2026-08-26 04:34 639233151357344052
330 ms 192.185.169.176
13 2026-08-26 04:17 639233141034116946
97 ms 192.185.169.176
12 2026-08-26 03:59 639233130828334142
4 ms 192.185.169.176
11 2026-08-26 03:42 639233120373450007
855 ms 192.185.169.176
10 2026-08-26 03:25 639233110066216193
97 ms 192.185.169.176
9 2026-08-26 02:32 639233078065410564
3 ms 192.185.169.176
8 2026-08-26 02:14 639233067787457832
196 ms 192.185.169.176
7 2026-08-26 01:57 639233057501801162
436 ms 192.185.169.176
6 2026-08-26 01:40 639233047089431703
208 ms 192.185.169.176
5 2026-08-26 01:23 639233036754790688
2009 ms 192.185.169.176
4 2026-08-26 01:06 639233026412602472
10 ms 192.185.169.176
3 2026-08-26 00:48 639233016064066127
2032 ms 192.185.169.176
2 2026-08-26 00:31 639233005922655772
343 ms 192.185.169.176
1 2026-08-26 00:14 639232995672256907
99 ms 192.185.169.176