DNS response history for ns.ritense.com

ns.ritense.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 33 DNS check records, 33 successful responses, 0 failed responses, and 290 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.ritense.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.28.147.150

Most recently resolved hosting IP on selected date

Successful Responses

33

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.ritense.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
33 2026-08-26 10:32 639233370841350248
2052 ms 52.28.147.150
32 2026-08-26 10:15 639233360361507238
5 ms 52.28.147.150
31 2026-08-26 09:57 639233350067824371
20 ms 52.28.147.150
30 2026-08-26 09:40 639233339545274518
18 ms 52.28.147.150
29 2026-08-26 09:23 639233329214918079
20 ms 52.28.147.150
28 2026-08-26 09:05 639233318749762337
101 ms 52.28.147.150
27 2026-08-26 08:48 639233308387917838
26 ms 52.28.147.150
26 2026-08-26 08:31 639233297961740122
88 ms 52.28.147.150
25 2026-08-26 08:13 639233287487159094
48 ms 52.28.147.150
24 2026-08-26 07:56 639233276995531707
6 ms 52.28.147.150
23 2026-08-26 07:38 639233266521568229
40 ms 52.28.147.150
22 2026-08-26 07:21 639233256081047431
26 ms 52.28.147.150
21 2026-08-26 06:27 639233223620132921
30 ms 52.28.147.150
20 2026-08-26 06:09 639233213287814244
21 ms 52.28.147.150
19 2026-08-26 05:52 639233202925983161
2032 ms 52.28.147.150
18 2026-08-26 05:35 639233192644780696
13 ms 52.28.147.150
17 2026-08-26 05:18 639233182401183833
5 ms 52.28.147.150
16 2026-08-26 05:01 639233172074181051
2091 ms 52.28.147.150
15 2026-08-26 04:44 639233161808421455
190 ms 52.28.147.150
14 2026-08-26 04:26 639233151357344052
121 ms 52.28.147.150
13 2026-08-26 04:09 639233141034116946
115 ms 52.28.147.150
12 2026-08-26 03:52 639233130828334142
36 ms 52.28.147.150
11 2026-08-26 03:35 639233120373450007
49 ms 52.28.147.150
10 2026-08-26 03:17 639233110066216193
19 ms 52.28.147.150
9 2026-08-26 02:24 639233078065410564
8 ms 52.28.147.150
8 2026-08-26 02:07 639233067787457832
80 ms 52.28.147.150
7 2026-08-26 01:50 639233057501801162
30 ms 52.28.147.150
6 2026-08-26 01:32 639233047089431703
13 ms 52.28.147.150
5 2026-08-26 01:15 639233036754790688
33 ms 52.28.147.150
4 2026-08-26 00:58 639233026412602472
21 ms 52.28.147.150
3 2026-08-26 00:41 639233016064066127
2066 ms 52.28.147.150
2 2026-08-26 00:24 639233005922655772
69 ms 52.28.147.150
1 2026-08-26 00:07 639232995672256907
70 ms 52.28.147.150