DNS response history for ns2.omkorea.org

ns2.omkorea.org 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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 539 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.omkorea.org.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

539 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 06:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.28.74.166

Most recently resolved hosting IP on selected date

Successful Responses

34

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.omkorea.org

Showing DNS history for 2026-08-24 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
34 2026-08-24 06:50 639231508078650885
2064 ms 139.28.74.166
33 2026-08-24 06:50 639231508078650885
2064 ms 193.24.127.88
32 2026-08-24 06:34 639231498210697093
323 ms 193.24.127.88
31 2026-08-24 06:34 639231498210697093
323 ms 139.28.74.166
30 2026-08-24 06:17 639231488109699360
61 ms 193.24.127.88
29 2026-08-24 06:17 639231488109699360
61 ms 139.28.74.166
28 2026-08-24 05:25 639231456772510692
80 ms 193.24.127.88
27 2026-08-24 05:25 639231456772510692
80 ms 139.28.74.166
26 2026-08-24 05:08 639231447084631185
67 ms 193.24.127.88
25 2026-08-24 05:08 639231447084631185
67 ms 139.28.74.166
24 2026-08-24 04:52 639231437208519473
2023 ms 139.28.74.166
23 2026-08-24 04:52 639231437208519473
2023 ms 193.24.127.88
22 2026-08-24 04:35 639231427209627490
2072 ms 139.28.74.166
21 2026-08-24 04:35 639231427209627490
2072 ms 193.24.127.88
20 2026-08-24 03:43 639231395791246644
58 ms 193.24.127.88
19 2026-08-24 03:43 639231395791246644
58 ms 139.28.74.166
18 2026-08-24 03:27 639231386075551458
5 ms 139.28.74.166
17 2026-08-24 03:27 639231386075551458
5 ms 193.24.127.88
16 2026-08-24 03:10 639231376208713791
2067 ms 193.24.127.88
15 2026-08-24 03:10 639231376208713791
2067 ms 139.28.74.166
14 2026-08-24 02:54 639231366170589276
69 ms 139.28.74.166
13 2026-08-24 02:54 639231366170589276
69 ms 193.24.127.88
12 2026-08-24 02:01 639231334732159368
9 ms 193.24.127.88
11 2026-08-24 02:01 639231334732159368
9 ms 139.28.74.166
10 2026-08-24 01:45 639231325035670078
65 ms 139.28.74.166
9 2026-08-24 01:45 639231325035670078
65 ms 193.24.127.88
8 2026-08-24 01:28 639231315132253837
47 ms 139.28.74.166
7 2026-08-24 01:28 639231315132253837
47 ms 193.24.127.88
6 2026-08-24 01:12 639231305014280808
60 ms 193.24.127.88
5 2026-08-24 01:12 639231305014280808
60 ms 139.28.74.166
4 2026-08-24 00:20 639231273779380675
2 ms 193.24.127.88
3 2026-08-24 00:20 639231273779380675
2 ms 139.28.74.166
2 2026-08-24 00:04 639231264180839154
94 ms 139.28.74.166
1 2026-08-24 00:04 639231264180839154
94 ms 193.24.127.88