DNS response history for ns2.ryoju819.com

ns2.ryoju819.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 26 DNS check records, 26 successful responses, 0 failed responses, and 493 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.ryoju819.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.112.213

Most recently resolved hosting IP on selected date

Successful Responses

26

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.ryoju819.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
26 2026-08-26 08:26 639233287487159094
560 ms 153.122.112.213
25 2026-08-26 08:08 639233276995531707
563 ms 153.122.112.213
24 2026-08-26 07:51 639233266521568229
551 ms 153.122.112.213
23 2026-08-26 07:33 639233256081047431
562 ms 153.122.112.213
22 2026-08-26 06:39 639233223620132921
556 ms 153.122.112.213
21 2026-08-26 06:22 639233213287814244
566 ms 153.122.112.213
20 2026-08-26 06:05 639233202925983161
571 ms 153.122.112.213
19 2026-08-26 05:47 639233192644780696
3 ms 153.122.112.213
18 2026-08-26 05:30 639233182401183833
547 ms 153.122.112.213
17 2026-08-26 05:13 639233172074181051
567 ms 153.122.112.213
16 2026-08-26 04:56 639233161808421455
552 ms 153.122.112.213
15 2026-08-26 04:39 639233151357344052
560 ms 153.122.112.213
14 2026-08-26 04:21 639233141034116946
565 ms 153.122.112.213
13 2026-08-26 04:04 639233130828334142
556 ms 153.122.112.213
12 2026-08-26 03:47 639233120373450007
555 ms 153.122.112.213
11 2026-08-26 03:30 639233110066216193
551 ms 153.122.112.213
10 2026-08-26 02:36 639233078065410564
528 ms 153.122.112.213
9 2026-08-26 02:19 639233067787457832
8 ms 153.122.112.213
8 2026-08-26 02:02 639233057501801162
550 ms 153.122.112.213
7 2026-08-26 01:45 639233047089431703
270 ms 153.122.112.213
6 2026-08-26 01:28 639233036754790688
278 ms 153.122.112.213
5 2026-08-26 01:10 639233026412602472
544 ms 153.122.112.213
4 2026-08-26 00:53 639233016064066127
548 ms 153.122.112.213
3 2026-08-26 00:36 639233005922655772
524 ms 153.122.112.213
2 2026-08-26 00:19 639232995672256907
527 ms 153.122.112.213
1 2026-08-26 00:02 639232985300872416
657 ms 153.122.112.213