DNS response history for ns.rinno.co.kr

ns.rinno.co.kr 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 36 DNS check records, 36 successful responses, 0 failed responses, and 463 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.rinno.co.kr.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

463 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.145.65.143

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 ns.rinno.co.kr

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
36 2026-08-26 11:57 639233414056832719
571 ms 218.145.65.143
35 2026-08-26 11:40 639233403515141099
584 ms 218.145.65.143
34 2026-08-26 10:45 639233370841350248
424 ms 218.145.65.143
33 2026-08-26 10:28 639233360361507238
576 ms 218.145.65.143
32 2026-08-26 10:10 639233350067824371
445 ms 218.145.65.143
31 2026-08-26 09:53 639233339545274518
442 ms 218.145.65.143
30 2026-08-26 09:36 639233329214918079
456 ms 218.145.65.143
29 2026-08-26 09:18 639233318749762337
443 ms 218.145.65.143
28 2026-08-26 09:01 639233308387917838
567 ms 218.145.65.143
27 2026-08-26 08:44 639233297961740122
791 ms 218.145.65.143
26 2026-08-26 08:26 639233287487159094
565 ms 218.145.65.143
25 2026-08-26 08:09 639233276995531707
287 ms 218.145.65.143
24 2026-08-26 07:51 639233266521568229
557 ms 218.145.65.143
23 2026-08-26 07:34 639233256081047431
283 ms 218.145.65.143
22 2026-08-26 06:40 639233223620132921
3 ms 218.145.65.143
21 2026-08-26 06:22 639233213287814244
564 ms 218.145.65.143
20 2026-08-26 06:05 639233202925983161
570 ms 218.145.65.143
19 2026-08-26 05:48 639233192644780696
278 ms 218.145.65.143
18 2026-08-26 05:31 639233182401183833
280 ms 218.145.65.143
17 2026-08-26 05:14 639233172074181051
583 ms 218.145.65.143
16 2026-08-26 04:56 639233161808421455
983 ms 218.145.65.143
15 2026-08-26 04:39 639233151357344052
566 ms 218.145.65.143
14 2026-08-26 04:22 639233141034116946
278 ms 218.145.65.143
13 2026-08-26 04:05 639233130828334142
560 ms 218.145.65.143
12 2026-08-26 03:48 639233120373450007
277 ms 218.145.65.143
11 2026-08-26 03:30 639233110066216193
574 ms 218.145.65.143
10 2026-08-26 02:37 639233078065410564
292 ms 218.145.65.143
9 2026-08-26 02:20 639233067787457832
568 ms 218.145.65.143
8 2026-08-26 02:03 639233057501801162
470 ms 218.145.65.143
7 2026-08-26 01:46 639233047089431703
555 ms 218.145.65.143
6 2026-08-26 01:28 639233036754790688
582 ms 218.145.65.143
5 2026-08-26 01:11 639233026412602472
4 ms 218.145.65.143
4 2026-08-26 00:54 639233016064066127
287 ms 218.145.65.143
3 2026-08-26 00:37 639233005922655772
559 ms 218.145.65.143
2 2026-08-26 00:20 639232995672256907
279 ms 218.145.65.143
1 2026-08-26 00:02 639232985300872416
582 ms 218.145.65.143