DNS response history for ns.samshinvalve.co.kr

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

30

Historical checks stored for this nameserver on selected date

Average Latency

573 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.10.2

Most recently resolved hosting IP on selected date

Successful Responses

30

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.samshinvalve.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
30 2026-08-26 09:36 639233329214918079
589 ms 192.168.10.2
29 2026-08-26 09:19 639233318749762337
582 ms 192.168.10.2
28 2026-08-26 09:01 639233308387917838
589 ms 192.168.10.2
27 2026-08-26 08:44 639233297961740122
583 ms 192.168.10.2
26 2026-08-26 08:27 639233287487159094
606 ms 192.168.10.2
25 2026-08-26 08:09 639233276995531707
573 ms 192.168.10.2
24 2026-08-26 07:52 639233266521568229
316 ms 192.168.10.2
23 2026-08-26 07:34 639233256081047431
575 ms 192.168.10.2
22 2026-08-26 06:40 639233223620132921
599 ms 192.168.10.2
21 2026-08-26 06:23 639233213287814244
571 ms 192.168.10.2
20 2026-08-26 06:06 639233202925983161
569 ms 192.168.10.2
19 2026-08-26 05:48 639233192644780696
585 ms 192.168.10.2
18 2026-08-26 05:31 639233182401183833
585 ms 192.168.10.2
17 2026-08-26 05:14 639233172074181051
575 ms 192.168.10.2
16 2026-08-26 04:57 639233161808421455
578 ms 192.168.10.2
15 2026-08-26 04:40 639233151357344052
572 ms 192.168.10.2
14 2026-08-26 04:22 639233141034116946
872 ms 192.168.10.2
13 2026-08-26 04:05 639233130828334142
582 ms 192.168.10.2
12 2026-08-26 03:48 639233120373450007
586 ms 192.168.10.2
11 2026-08-26 03:31 639233110066216193
576 ms 192.168.10.2
10 2026-08-26 02:37 639233078065410564
579 ms 192.168.10.2
9 2026-08-26 02:20 639233067787457832
603 ms 192.168.10.2
8 2026-08-26 02:03 639233057501801162
582 ms 192.168.10.2
7 2026-08-26 01:46 639233047089431703
576 ms 192.168.10.2
6 2026-08-26 01:29 639233036754790688
574 ms 192.168.10.2
5 2026-08-26 01:11 639233026412602472
590 ms 192.168.10.2
4 2026-08-26 00:54 639233016064066127
583 ms 192.168.10.2
3 2026-08-26 00:37 639233005922655772
588 ms 192.168.10.2
2 2026-08-26 00:20 639232995672256907
582 ms 192.168.10.2
1 2026-08-26 00:03 639232985300872416
281 ms 220.123.204.2