DNS response history for ns02.yaplu-k.org

ns02.yaplu-k.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 33 DNS check records, 33 successful responses, 0 failed responses, and 291 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 ns02.yaplu-k.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

291 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

85.215.151.118

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns02.yaplu-k.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
33 2026-08-24 13:41 639231755868832964
59 ms 85.215.151.118
32 2026-08-24 13:23 639231745628278877
49 ms 85.215.151.118
31 2026-08-24 13:06 639231735407682062
58 ms 85.215.151.118
30 2026-08-24 12:14 639231703815441688
2050 ms 85.215.151.118
29 2026-08-24 11:57 639231693747052549
7 ms 85.215.151.118
28 2026-08-24 11:40 639231683712487276
56 ms 85.215.151.118
27 2026-08-24 11:23 639231673513573868
163 ms 85.215.151.118
26 2026-08-24 10:30 639231641791249939
37 ms 85.215.151.118
25 2026-08-24 10:14 639231631866211033
100 ms 85.215.151.118
24 2026-08-24 09:57 639231621644955316
26 ms 85.215.151.118
23 2026-08-24 09:40 639231611478799259
30 ms 85.215.151.118
22 2026-08-24 08:47 639231579923718211
99 ms 85.215.151.118
21 2026-08-24 08:30 639231569810702936
6 ms 85.215.151.118
20 2026-08-24 08:14 639231559762411619
22 ms 85.215.151.118
19 2026-08-24 07:57 639231549663595407
4 ms 85.215.151.118
18 2026-08-24 07:04 639231518076817246
22 ms 85.215.151.118
17 2026-08-24 06:48 639231508078650885
120 ms 85.215.151.118
16 2026-08-24 06:31 639231498210697093
70 ms 85.215.151.118
15 2026-08-24 06:14 639231488109699360
55 ms 85.215.151.118
14 2026-08-24 05:22 639231456772510692
50 ms 85.215.151.118
13 2026-08-24 05:06 639231447084631185
19 ms 85.215.151.118
12 2026-08-24 04:49 639231437208519473
20 ms 85.215.151.118
11 2026-08-24 04:33 639231427209627490
42 ms 85.215.151.118
10 2026-08-24 03:40 639231395791246644
10 ms 85.215.151.118
9 2026-08-24 03:24 639231386075551458
3 ms 85.215.151.118
8 2026-08-24 03:08 639231376208713791
157 ms 85.215.151.118
7 2026-08-24 02:51 639231366170589276
3 ms 85.215.151.118
6 2026-08-24 01:59 639231334732159368
23 ms 85.215.151.118
5 2026-08-24 01:42 639231325035670078
68 ms 85.215.151.118
4 2026-08-24 01:26 639231315132253837
58 ms 85.215.151.118
3 2026-08-24 01:09 639231305014280808
2027 ms 85.215.151.118
2 2026-08-24 00:17 639231273779380675
2024 ms 85.215.151.118
1 2026-08-24 00:01 639231264180839154
2082 ms 85.215.151.118