DNS response history for ns2.hompy119.kr

ns2.hompy119.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 31 DNS check records, 31 successful responses, 0 failed responses, and 877 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.hompy119.kr.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

877 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

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

31

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.hompy119.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
31 2026-08-25 10:22 639232492740373468
1814 ms 121.125.73.38
30 2026-08-25 10:05 639232482235303141
612 ms 121.125.73.38
29 2026-08-25 09:48 639232471861770303
611 ms 121.125.73.38
28 2026-08-25 09:31 639232461630217327
1423 ms 121.125.73.38
27 2026-08-25 09:13 639232451282965990
841 ms 121.125.73.38
26 2026-08-25 08:56 639232440814614938
597 ms 121.125.73.38
25 2026-08-25 08:39 639232430410720425
695 ms 121.125.73.38
24 2026-08-25 08:21 639232420003096185
1291 ms 121.125.73.38
23 2026-08-25 08:04 639232409467287444
605 ms 121.125.73.38
22 2026-08-25 07:47 639232399077195997
601 ms 121.125.73.38
21 2026-08-25 07:29 639232388731528337
612 ms 121.125.73.38
20 2026-08-25 07:12 639232378288598612
623 ms 121.125.73.38
19 2026-08-25 06:18 639232346196373643
609 ms 121.125.73.38
18 2026-08-25 06:01 639232336112370741
605 ms 121.125.73.38
17 2026-08-25 05:44 639232326146508970
1232 ms 121.125.73.38
16 2026-08-25 05:28 639232316189381720
870 ms 121.125.73.38
15 2026-08-25 05:11 639232306217998913
583 ms 121.125.73.38
14 2026-08-25 04:55 639232296255744174
591 ms 121.125.73.38
13 2026-08-25 04:38 639232286095760789
1689 ms 121.125.73.38
12 2026-08-25 04:21 639232276086186273
1182 ms 121.125.73.38
11 2026-08-25 04:04 639232265900986425
597 ms 121.125.73.38
10 2026-08-25 03:47 639232255723518075
601 ms 121.125.73.38
9 2026-08-25 03:30 639232245484452890
1982 ms 121.125.73.38
8 2026-08-25 03:13 639232235157175331
609 ms 121.125.73.38
7 2026-08-25 02:20 639232203197189095
596 ms 121.125.73.38
6 2026-08-25 02:03 639232192844564298
614 ms 121.125.73.38
5 2026-08-25 01:45 639232182496008942
1678 ms 121.125.73.38
4 2026-08-25 01:28 639232172197053132
1200 ms 121.125.73.38
3 2026-08-25 00:35 639232140250307418
613 ms 121.125.73.38
2 2026-08-25 00:18 639232129927860324
611 ms 121.125.73.38
1 2026-08-25 00:00 639232119551972438
388 ms 121.125.73.38