DNS response history for ns3.findhappy.kr

ns3.findhappy.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 610 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 ns3.findhappy.kr.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

610 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns3.findhappy.kr

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:17 639234253963286387
559 ms 116.126.143.225
34 2026-08-27 11:00 639234243654907465
565 ms 116.126.143.225
33 2026-08-27 10:42 639234233269654413
487 ms 116.126.143.225
32 2026-08-27 10:25 639234222943951923
516 ms 116.126.143.225
31 2026-08-27 10:08 639234212558002823
2302 ms 116.126.143.225
30 2026-08-27 09:51 639234202117531850
493 ms 116.126.143.225
29 2026-08-27 09:33 639234191649612722
577 ms 116.126.143.225
28 2026-08-27 09:16 639234181105879568
407 ms 116.126.143.225
27 2026-08-27 08:58 639234170713214496
575 ms 116.126.143.225
26 2026-08-27 08:41 639234160341037652
570 ms 116.126.143.225
25 2026-08-27 08:23 639234149799404224
624 ms 116.126.143.225
24 2026-08-27 08:06 639234139553286469
849 ms 116.126.143.225
23 2026-08-27 07:12 639234107183588293
519 ms 116.126.143.225
22 2026-08-27 06:55 639234096905435724
587 ms 116.126.143.225
21 2026-08-27 06:38 639234086579410775
572 ms 116.126.143.225
20 2026-08-27 06:21 639234076291157956
559 ms 116.126.143.225
19 2026-08-27 06:04 639234065981939454
490 ms 116.126.143.225
18 2026-08-27 05:46 639234055548642997
554 ms 116.126.143.225
17 2026-08-27 05:29 639234045267979603
790 ms 116.126.143.225
16 2026-08-27 05:12 639234034999717463
553 ms 116.126.143.225
15 2026-08-27 04:55 639234024739225358
555 ms 116.126.143.225
14 2026-08-27 04:38 639234014311170162
583 ms 116.126.143.225
13 2026-08-27 04:20 639234003806017640
564 ms 116.126.143.225
12 2026-08-27 04:03 639233993356203030
571 ms 116.126.143.225
11 2026-08-27 03:09 639233961301716608
571 ms 116.126.143.225
10 2026-08-27 02:52 639233950834200647
559 ms 116.126.143.225
9 2026-08-27 02:34 639233940431849026
558 ms 116.126.143.225
8 2026-08-27 02:17 639233930110596398
553 ms 116.126.143.225
7 2026-08-27 02:00 639233919705434540
497 ms 116.126.143.225
6 2026-08-27 01:43 639233909452807845
573 ms 116.126.143.225
5 2026-08-27 01:25 639233899096420820
564 ms 116.126.143.225
4 2026-08-27 01:08 639233888707824939
517 ms 116.126.143.225
3 2026-08-27 00:51 639233878461203802
520 ms 116.126.143.225
2 2026-08-27 00:34 639233868060868209
449 ms 116.126.143.225
1 2026-08-27 00:16 639233857450922991
565 ms 116.126.143.225