DNS response history for ns2.yoolk.ninja

ns2.yoolk.ninja 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 36 DNS check records, 35 successful responses, 1 failed responses, and 255 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.yoolk.ninja.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

255 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.135.220.188

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.yoolk.ninja

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
36 2026-08-24 15:12 639231807961539652
30 ms 147.135.220.188
35 2026-08-24 14:55 639231797631669865
41 ms 147.135.220.188
34 2026-08-24 14:02 639231765923559455
9 ms 147.135.220.188
33 2026-08-24 13:45 639231755868832964
63 ms 147.135.220.188
32 2026-08-24 13:29 639231745628278877
48 ms 147.135.220.188
31 2026-08-24 13:11 639231735407682062
2023 ms 147.135.220.188
30 2026-08-24 12:19 639231703815441688
43 ms 147.135.220.188
29 2026-08-24 12:02 639231693747052549
-
28 2026-08-24 11:45 639231683712487276
29 ms 147.135.220.188
27 2026-08-24 11:28 639231673513573868
50 ms 147.135.220.188
26 2026-08-24 10:35 639231641791249939
4 ms 147.135.220.188
25 2026-08-24 10:19 639231631866211033
34 ms 147.135.220.188
24 2026-08-24 10:02 639231621644955316
42 ms 147.135.220.188
23 2026-08-24 09:45 639231611478799259
28 ms 147.135.220.188
22 2026-08-24 08:52 639231579923718211
9 ms 147.135.220.188
21 2026-08-24 08:36 639231569810702936
4 ms 147.135.220.188
20 2026-08-24 08:19 639231559762411619
24 ms 147.135.220.188
19 2026-08-24 08:02 639231549663595407
4 ms 147.135.220.188
18 2026-08-24 07:09 639231518076817246
2018 ms 147.135.220.188
17 2026-08-24 06:53 639231508078650885
9 ms 147.135.220.188
16 2026-08-24 06:36 639231498210697093
38 ms 147.135.220.188
15 2026-08-24 06:19 639231488109699360
2017 ms 147.135.220.188
14 2026-08-24 05:27 639231456772510692
4 ms 147.135.220.188
13 2026-08-24 05:11 639231447084631185
57 ms 147.135.220.188
12 2026-08-24 04:54 639231437208519473
46 ms 147.135.220.188
11 2026-08-24 04:38 639231427209627490
29 ms 147.135.220.188
10 2026-08-24 03:45 639231395791246644
14 ms 147.135.220.188
9 2026-08-24 03:29 639231386075551458
3 ms 147.135.220.188
8 2026-08-24 03:13 639231376208713791
87 ms 147.135.220.188
7 2026-08-24 02:56 639231366170589276
27 ms 147.135.220.188
6 2026-08-24 02:04 639231334732159368
8 ms 147.135.220.188
5 2026-08-24 01:47 639231325035670078
25 ms 147.135.220.188
4 2026-08-24 01:31 639231315132253837
2016 ms 147.135.220.188
3 2026-08-24 01:14 639231305014280808
24 ms 147.135.220.188
2 2026-08-24 00:22 639231273779380675
4 ms 147.135.220.188
1 2026-08-24 00:06 639231264180839154
3 ms 147.135.220.188