DNS response history for ns2.rycks.com

ns2.rycks.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, 32 successful responses, 1 failed responses, and 168 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.rycks.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

168 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

213.186.35.179

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.rycks.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
22 ms 213.186.35.179
32 2026-08-26 10:15 639233360361507238
51 ms 213.186.35.179
31 2026-08-26 09:57 639233350067824371
50 ms 213.186.35.179
30 2026-08-26 09:40 639233339545274518
35 ms 213.186.35.179
29 2026-08-26 09:23 639233329214918079
34 ms 213.186.35.179
28 2026-08-26 09:05 639233318749762337
34 ms 213.186.35.179
27 2026-08-26 08:48 639233308387917838
33 ms 213.186.35.179
26 2026-08-26 08:30 639233297961740122
44 ms 213.186.35.179
25 2026-08-26 08:13 639233287487159094
36 ms 213.186.35.179
24 2026-08-26 07:56 639233276995531707
37 ms 213.186.35.179
23 2026-08-26 07:38 639233266521568229
51 ms 213.186.35.179
22 2026-08-26 07:21 639233256081047431
33 ms 213.186.35.179
21 2026-08-26 06:27 639233223620132921
60 ms 213.186.35.179
20 2026-08-26 06:09 639233213287814244
42 ms 213.186.35.179
19 2026-08-26 05:52 639233202925983161
60 ms 213.186.35.179
18 2026-08-26 05:35 639233192644780696
49 ms 213.186.35.179
17 2026-08-26 05:18 639233182401183833
42 ms 213.186.35.179
16 2026-08-26 05:01 639233172074181051
34 ms 213.186.35.179
15 2026-08-26 04:44 639233161808421455
13 ms 213.186.35.179
14 2026-08-26 04:26 639233151357344052
39 ms 213.186.35.179
13 2026-08-26 04:09 639233141034116946
34 ms 213.186.35.179
12 2026-08-26 03:52 639233130828334142
2049 ms 213.186.35.179
11 2026-08-26 03:35 639233120373450007
32 ms 213.186.35.179
10 2026-08-26 03:17 639233110066216193
30 ms 213.186.35.179
9 2026-08-26 02:24 639233078065410564
74 ms 213.186.35.179
8 2026-08-26 02:07 639233067787457832
32 ms 213.186.35.179
7 2026-08-26 01:50 639233057501801162
32 ms 213.186.35.179
6 2026-08-26 01:32 639233047089431703
82 ms 213.186.35.179
5 2026-08-26 01:15 639233036754790688
2031 ms 213.186.35.179
4 2026-08-26 00:58 639233026412602472
-
3 2026-08-26 00:41 639233016064066127
70 ms 213.186.35.179
2 2026-08-26 00:24 639233005922655772
34 ms 213.186.35.179
1 2026-08-26 00:07 639232995672256907
77 ms 213.186.35.179