DNS response history for ns2.yoco.ws

ns2.yoco.ws 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 35 DNS check records, 35 successful responses, 0 failed responses, and 231 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.yoco.ws.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

231 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.229.174

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 ns2.yoco.ws

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
35 2026-08-24 14:59 639231797631669865
337 ms 162.240.229.174
34 2026-08-24 14:06 639231765923559455
200 ms 162.240.229.174
33 2026-08-24 13:50 639231755868832964
339 ms 162.240.229.174
32 2026-08-24 13:33 639231745628278877
174 ms 162.240.229.174
31 2026-08-24 13:15 639231735407682062
4 ms 162.240.229.174
30 2026-08-24 12:23 639231703815441688
200 ms 162.240.229.174
29 2026-08-24 12:06 639231693747052549
344 ms 162.240.229.174
28 2026-08-24 11:49 639231683712487276
2008 ms 162.240.229.174
27 2026-08-24 11:32 639231673513573868
343 ms 162.240.229.174
26 2026-08-24 10:39 639231641791249939
198 ms 162.240.229.174
25 2026-08-24 10:23 639231631866211033
16 ms 162.240.229.174
24 2026-08-24 10:06 639231621644955316
379 ms 162.240.229.174
23 2026-08-24 09:49 639231611478799259
5 ms 162.240.229.174
22 2026-08-24 08:56 639231579923718211
318 ms 162.240.229.174
21 2026-08-24 08:40 639231569810702936
221 ms 162.240.229.174
20 2026-08-24 08:23 639231559762411619
342 ms 162.240.229.174
19 2026-08-24 08:06 639231549663595407
341 ms 162.240.229.174
18 2026-08-24 07:13 639231518076817246
8 ms 162.240.229.174
17 2026-08-24 06:57 639231508078650885
4 ms 162.240.229.174
16 2026-08-24 06:40 639231498210697093
336 ms 162.240.229.174
15 2026-08-24 06:24 639231488109699360
343 ms 162.240.229.174
14 2026-08-24 05:31 639231456772510692
3 ms 162.240.229.174
13 2026-08-24 05:15 639231447084631185
203 ms 162.240.229.174
12 2026-08-24 04:58 639231437208519473
3 ms 162.240.229.174
11 2026-08-24 04:42 639231427209627490
3 ms 162.240.229.174
10 2026-08-24 03:49 639231395791246644
170 ms 162.240.229.174
9 2026-08-24 03:33 639231386075551458
194 ms 162.240.229.174
8 2026-08-24 03:17 639231376208713791
341 ms 162.240.229.174
7 2026-08-24 03:00 639231366170589276
170 ms 162.240.229.174
6 2026-08-24 02:08 639231334732159368
346 ms 162.240.229.174
5 2026-08-24 01:51 639231325035670078
10 ms 162.240.229.174
4 2026-08-24 01:35 639231315132253837
11 ms 162.240.229.174
3 2026-08-24 01:18 639231305014280808
3 ms 162.240.229.174
2 2026-08-24 00:26 639231273779380675
3 ms 162.240.229.174
1 2026-08-24 00:10 639231264180839154
170 ms 162.240.229.174