DNS response history for ns2.diosoft.kr

ns2.diosoft.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-30. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 778 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.diosoft.kr.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

778 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.125.73.38

Most recently resolved hosting IP on selected date

Successful Responses

32

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.diosoft.kr

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
32 2026-08-30 10:31 639236817708615077
1373 ms 121.125.73.38
31 2026-08-30 09:37 639236785770651804
587 ms 121.125.73.38
30 2026-08-30 09:21 639236775820686373
619 ms 121.125.73.38
29 2026-08-30 09:04 639236765768339082
579 ms 121.125.73.38
28 2026-08-30 08:47 639236755602384085
1201 ms 121.125.73.38
27 2026-08-30 08:30 639236745600094925
598 ms 121.125.73.38
26 2026-08-30 08:14 639236735311262753
463 ms 121.125.73.38
25 2026-08-30 07:56 639236724996745235
1210 ms 121.125.73.38
24 2026-08-30 07:39 639236714839899761
590 ms 121.125.73.38
23 2026-08-30 07:22 639236704748431488
595 ms 121.125.73.38
22 2026-08-30 07:05 639236694430128550
592 ms 121.125.73.38
21 2026-08-30 06:48 639236684143292417
605 ms 121.125.73.38
20 2026-08-30 06:31 639236673972499943
619 ms 121.125.73.38
19 2026-08-30 05:38 639236642126522802
600 ms 121.125.73.38
18 2026-08-30 05:21 639236632183518198
1693 ms 121.125.73.38
17 2026-08-30 05:05 639236622289312589
594 ms 121.125.73.38
16 2026-08-30 04:48 639236612490676525
996 ms 121.125.73.38
15 2026-08-30 04:32 639236602582494852
613 ms 121.125.73.38
14 2026-08-30 04:15 639236592511706469
1922 ms 121.125.73.38
13 2026-08-30 03:58 639236582441006869
498 ms 121.125.73.38
12 2026-08-30 03:42 639236572478785089
1379 ms 121.125.73.38
11 2026-08-30 03:25 639236562556749999
596 ms 121.125.73.38
10 2026-08-30 03:08 639236552353482281
488 ms 121.125.73.38
9 2026-08-30 02:51 639236542188881607
1484 ms 121.125.73.38
8 2026-08-30 02:34 639236531885440105
454 ms 121.125.73.38
7 2026-08-30 01:41 639236499922985383
471 ms 121.125.73.38
6 2026-08-30 01:24 639236489713594431
594 ms 121.125.73.38
5 2026-08-30 01:07 639236479750443901
604 ms 121.125.73.38
4 2026-08-30 00:50 639236469719936375
583 ms 121.125.73.38
3 2026-08-30 00:34 639236459579244885
614 ms 121.125.73.38
2 2026-08-30 00:17 639236449582837549
505 ms 121.125.73.38
1 2026-08-30 00:00 639236439461653110
589 ms 121.125.73.38