DNS response history for hk2.yunapp.club

hk2.yunapp.club 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 216 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 hk2.yunapp.club.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

216 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.143.46.185

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 hk2.yunapp.club

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 11:11 639232524938080723
40 ms 104.143.46.185
30 2026-08-25 10:17 639232492740373468
38 ms 104.143.46.185
29 2026-08-25 10:00 639232482235303141
34 ms 104.143.46.185
28 2026-08-25 09:42 639232471861770303
24 ms 104.143.46.185
27 2026-08-25 09:25 639232461630217327
33 ms 104.143.46.185
26 2026-08-25 09:08 639232451282965990
65 ms 104.143.46.185
25 2026-08-25 08:51 639232440814614938
36 ms 104.143.46.185
24 2026-08-25 08:33 639232430410720425
275 ms 104.143.46.185
23 2026-08-25 08:16 639232420003096185
41 ms 104.143.46.185
22 2026-08-25 07:58 639232409467287444
24 ms 104.143.46.185
21 2026-08-25 07:41 639232399077195997
39 ms 104.143.46.185
20 2026-08-25 07:24 639232388731528337
251 ms 104.143.46.185
19 2026-08-25 07:06 639232378288598612
253 ms 104.143.46.185
18 2026-08-25 06:13 639232346196373643
39 ms 104.143.46.185
17 2026-08-25 05:56 639232336112370741
29 ms 104.143.46.185
16 2026-08-25 05:39 639232326146508970
152 ms 104.143.46.185
15 2026-08-25 05:23 639232316189381720
2013 ms 104.143.46.185
14 2026-08-25 05:06 639232306217998913
37 ms 104.143.46.185
13 2026-08-25 04:49 639232296255744174
23 ms 104.143.46.185
12 2026-08-25 04:33 639232286095760789
33 ms 104.143.46.185
11 2026-08-25 04:16 639232276086186273
34 ms 104.143.46.185
10 2026-08-25 03:59 639232265900986425
13 ms 104.143.46.185
9 2026-08-25 03:42 639232255723518075
42 ms 104.143.46.185
8 2026-08-25 03:25 639232245484452890
2217 ms 104.143.46.185
7 2026-08-25 03:08 639232235157175331
242 ms 104.143.46.185
6 2026-08-25 02:14 639232203197189095
275 ms 104.143.46.185
5 2026-08-25 01:57 639232192844564298
35 ms 104.143.46.185
4 2026-08-25 01:40 639232182496008942
36 ms 104.143.46.185
3 2026-08-25 01:23 639232172197053132
34 ms 104.143.46.185
2 2026-08-25 00:29 639232140250307418
262 ms 104.143.46.185
1 2026-08-25 00:12 639232129927860324
33 ms 104.143.46.185