DNS response history for ns2.ozweb.co.kr

ns2.ozweb.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 552 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.ozweb.co.kr.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

552 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:30

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

28

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.ozweb.co.kr

Showing DNS history for 2026-08-25 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
28 2026-08-25 09:30 639232461630217327
485 ms 121.125.73.38
27 2026-08-25 09:13 639232451282965990
602 ms 121.125.73.38
26 2026-08-25 08:56 639232440814614938
592 ms 121.125.73.38
25 2026-08-25 08:38 639232430410720425
640 ms 121.125.73.38
24 2026-08-25 08:21 639232420003096185
483 ms 121.125.73.38
23 2026-08-25 08:03 639232409467287444
599 ms 121.125.73.38
22 2026-08-25 07:46 639232399077195997
624 ms 121.125.73.38
21 2026-08-25 07:29 639232388731528337
615 ms 121.125.73.38
20 2026-08-25 07:11 639232378288598612
606 ms 121.125.73.38
19 2026-08-25 06:17 639232346196373643
611 ms 121.125.73.38
18 2026-08-25 06:01 639232336112370741
608 ms 121.125.73.38
17 2026-08-25 05:44 639232326146508970
347 ms 121.125.73.38
16 2026-08-25 05:27 639232316189381720
291 ms 121.125.73.38
15 2026-08-25 05:11 639232306217998913
469 ms 121.125.73.38
14 2026-08-25 04:54 639232296255744174
601 ms 121.125.73.38
13 2026-08-25 04:37 639232286095760789
482 ms 121.125.73.38
12 2026-08-25 04:20 639232276086186273
496 ms 121.125.73.38
11 2026-08-25 04:04 639232265900986425
600 ms 121.125.73.38
10 2026-08-25 03:47 639232255723518075
600 ms 121.125.73.38
9 2026-08-25 03:30 639232245484452890
487 ms 121.125.73.38
8 2026-08-25 03:13 639232235157175331
499 ms 121.125.73.38
7 2026-08-25 02:19 639232203197189095
595 ms 121.125.73.38
6 2026-08-25 02:02 639232192844564298
604 ms 121.125.73.38
5 2026-08-25 01:45 639232182496008942
486 ms 121.125.73.38
4 2026-08-25 01:28 639232172197053132
623 ms 121.125.73.38
3 2026-08-25 00:34 639232140250307418
604 ms 121.125.73.38
2 2026-08-25 00:17 639232129927860324
609 ms 121.125.73.38
1 2026-08-25 00:00 639232119551972438
607 ms 121.125.73.38