DNS response history for ns2.ryrpy.com

ns2.ryrpy.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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 370 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.ryrpy.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

370 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

140.235.100.5

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 ns2.ryrpy.com

Showing DNS history for 2026-08-30 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-30 11:52 639236867916029489
420 ms 140.235.100.5
35 2026-08-30 11:36 639236858088772005
369 ms 140.235.100.5
34 2026-08-30 11:19 639236848158742395
366 ms 140.235.100.5
33 2026-08-30 11:03 639236838137395574
190 ms 140.235.100.5
32 2026-08-30 10:46 639236827967386881
365 ms 140.235.100.5
31 2026-08-30 10:29 639236817708615077
363 ms 140.235.100.5
30 2026-08-30 09:36 639236785770651804
393 ms 140.235.100.5
29 2026-08-30 09:19 639236775820686373
364 ms 140.235.100.5
28 2026-08-30 09:02 639236765768339082
366 ms 140.235.100.5
27 2026-08-30 08:45 639236755602384085
390 ms 140.235.100.5
26 2026-08-30 08:28 639236745600094925
363 ms 140.235.100.5
25 2026-08-30 08:12 639236735311262753
364 ms 140.235.100.5
24 2026-08-30 07:54 639236724996745235
363 ms 140.235.100.5
23 2026-08-30 07:37 639236714839899761
366 ms 140.235.100.5
22 2026-08-30 07:20 639236704748431488
369 ms 140.235.100.5
21 2026-08-30 07:04 639236694430128550
370 ms 140.235.100.5
20 2026-08-30 06:46 639236684143292417
362 ms 140.235.100.5
19 2026-08-30 06:29 639236673972499943
366 ms 140.235.100.5
18 2026-08-30 05:36 639236642126522802
366 ms 140.235.100.5
17 2026-08-30 05:19 639236632183518198
362 ms 140.235.100.5
16 2026-08-30 05:03 639236622289312589
363 ms 140.235.100.5
15 2026-08-30 04:46 639236612490676525
362 ms 140.235.100.5
14 2026-08-30 04:30 639236602582494852
364 ms 140.235.100.5
13 2026-08-30 04:14 639236592511706469
370 ms 140.235.100.5
12 2026-08-30 03:57 639236582441006869
364 ms 140.235.100.5
11 2026-08-30 03:40 639236572478785089
597 ms 140.235.100.5
10 2026-08-30 03:23 639236562556749999
363 ms 140.235.100.5
9 2026-08-30 03:07 639236552353482281
363 ms 140.235.100.5
8 2026-08-30 02:50 639236542188881607
365 ms 140.235.100.5
7 2026-08-30 02:33 639236531885440105
370 ms 140.235.100.5
6 2026-08-30 01:39 639236499922985383
381 ms 140.235.100.5
5 2026-08-30 01:22 639236489713594431
372 ms 140.235.100.5
4 2026-08-30 01:05 639236479750443901
369 ms 140.235.100.5
3 2026-08-30 00:49 639236469719936375
358 ms 140.235.100.5
2 2026-08-30 00:32 639236459579244885
367 ms 140.235.100.5
1 2026-08-30 00:15 639236449582837549
365 ms 140.235.100.5