DNS response history for ns.ripplestech.com

ns.ripplestech.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 404 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 ns.ripplestech.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

404 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.167.172.167

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 ns.ripplestech.com

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 10:42 639233370841350248
122 ms 69.167.172.167
33 2026-08-26 10:25 639233360361507238
230 ms 69.167.172.167
32 2026-08-26 10:07 639233350067824371
225 ms 69.167.172.167
31 2026-08-26 09:50 639233339545274518
235 ms 69.167.172.167
30 2026-08-26 09:33 639233329214918079
233 ms 69.167.172.167
29 2026-08-26 09:15 639233318749762337
230 ms 69.167.172.167
28 2026-08-26 08:58 639233308387917838
2149 ms 69.167.172.167
27 2026-08-26 08:41 639233297961740122
232 ms 69.167.172.167
26 2026-08-26 08:23 639233287487159094
122 ms 69.167.172.167
25 2026-08-26 08:06 639233276995531707
232 ms 69.167.172.167
24 2026-08-26 07:48 639233266521568229
175 ms 69.167.172.167
23 2026-08-26 07:31 639233256081047431
244 ms 69.167.172.167
22 2026-08-26 06:37 639233223620132921
236 ms 69.167.172.167
21 2026-08-26 06:20 639233213287814244
237 ms 69.167.172.167
20 2026-08-26 06:02 639233202925983161
346 ms 69.167.172.167
19 2026-08-26 05:45 639233192644780696
235 ms 69.167.172.167
18 2026-08-26 05:28 639233182401183833
122 ms 69.167.172.167
17 2026-08-26 05:11 639233172074181051
564 ms 69.167.172.167
16 2026-08-26 04:54 639233161808421455
228 ms 69.167.172.167
15 2026-08-26 04:37 639233151357344052
230 ms 69.167.172.167
14 2026-08-26 04:19 639233141034116946
146 ms 69.167.172.167
13 2026-08-26 04:02 639233130828334142
244 ms 69.167.172.167
12 2026-08-26 03:45 639233120373450007
238 ms 69.167.172.167
11 2026-08-26 03:27 639233110066216193
233 ms 69.167.172.167
10 2026-08-26 02:34 639233078065410564
227 ms 69.167.172.167
9 2026-08-26 02:17 639233067787457832
2148 ms 69.167.172.167
8 2026-08-26 02:00 639233057501801162
238 ms 69.167.172.167
7 2026-08-26 01:43 639233047089431703
234 ms 69.167.172.167
6 2026-08-26 01:25 639233036754790688
227 ms 69.167.172.167
5 2026-08-26 01:08 639233026412602472
2315 ms 69.167.172.167
4 2026-08-26 00:51 639233016064066127
143 ms 69.167.172.167
3 2026-08-26 00:34 639233005922655772
224 ms 69.167.172.167
2 2026-08-26 00:17 639232995672256907
237 ms 69.167.172.167
1 2026-08-26 00:00 639232985300872416
243 ms 69.167.172.167