DNS response history for ns2.ryuunji.net

ns2.ryuunji.net 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 35 DNS check records, 35 successful responses, 0 failed responses, and 430 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.ryuunji.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

430 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.167.23.51

Most recently resolved hosting IP on selected date

Successful Responses

35

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.ryuunji.net

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
35 2026-08-26 11:39 639233403515141099
2286 ms 210.167.23.51
34 2026-08-26 10:44 639233370841350248
566 ms 210.167.23.51
33 2026-08-26 10:27 639233360361507238
519 ms 210.167.23.51
32 2026-08-26 10:10 639233350067824371
529 ms 210.167.23.51
31 2026-08-26 09:52 639233339545274518
280 ms 210.167.23.51
30 2026-08-26 09:35 639233329214918079
556 ms 210.167.23.51
29 2026-08-26 09:18 639233318749762337
6 ms 210.167.23.51
28 2026-08-26 09:00 639233308387917838
6 ms 210.167.23.51
27 2026-08-26 08:43 639233297961740122
555 ms 210.167.23.51
26 2026-08-26 08:25 639233287487159094
4 ms 210.167.23.51
25 2026-08-26 08:08 639233276995531707
556 ms 210.167.23.51
24 2026-08-26 07:50 639233266521568229
564 ms 210.167.23.51
23 2026-08-26 07:33 639233256081047431
559 ms 210.167.23.51
22 2026-08-26 06:39 639233223620132921
551 ms 210.167.23.51
21 2026-08-26 06:22 639233213287814244
10 ms 210.167.23.51
20 2026-08-26 06:04 639233202925983161
549 ms 210.167.23.51
19 2026-08-26 05:47 639233192644780696
9 ms 210.167.23.51
18 2026-08-26 05:30 639233182401183833
554 ms 210.167.23.51
17 2026-08-26 05:13 639233172074181051
567 ms 210.167.23.51
16 2026-08-26 04:56 639233161808421455
553 ms 210.167.23.51
15 2026-08-26 04:39 639233151357344052
557 ms 210.167.23.51
14 2026-08-26 04:21 639233141034116946
283 ms 210.167.23.51
13 2026-08-26 04:04 639233130828334142
274 ms 210.167.23.51
12 2026-08-26 03:47 639233120373450007
570 ms 210.167.23.51
11 2026-08-26 03:29 639233110066216193
275 ms 210.167.23.51
10 2026-08-26 02:36 639233078065410564
541 ms 210.167.23.51
9 2026-08-26 02:19 639233067787457832
277 ms 210.167.23.51
8 2026-08-26 02:02 639233057501801162
528 ms 210.167.23.51
7 2026-08-26 01:45 639233047089431703
555 ms 210.167.23.51
6 2026-08-26 01:27 639233036754790688
554 ms 210.167.23.51
5 2026-08-26 01:10 639233026412602472
10 ms 210.167.23.51
4 2026-08-26 00:53 639233016064066127
557 ms 210.167.23.51
3 2026-08-26 00:36 639233005922655772
3 ms 210.167.23.51
2 2026-08-26 00:19 639232995672256907
276 ms 210.167.23.51
1 2026-08-26 00:02 639232985300872416
4 ms 210.167.23.51