DNS response history for ns3.yandk.info

ns3.yandk.info 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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 609 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.yandk.info.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

609 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.167.17.179

Most recently resolved hosting IP on selected date

Successful Responses

29

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.yandk.info

Showing DNS history for 2026-08-26 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
29 2026-08-26 09:18 639233318749762337
776 ms 210.167.17.179
28 2026-08-26 09:00 639233308387917838
802 ms 210.167.17.179
27 2026-08-26 08:43 639233297961740122
678 ms 210.167.17.179
26 2026-08-26 08:26 639233287487159094
806 ms 210.167.17.179
25 2026-08-26 08:08 639233276995531707
700 ms 210.167.17.179
24 2026-08-26 07:51 639233266521568229
563 ms 210.167.17.179
23 2026-08-26 07:33 639233256081047431
793 ms 210.167.17.179
22 2026-08-26 06:39 639233223620132921
711 ms 210.167.17.179
21 2026-08-26 06:22 639233213287814244
573 ms 210.167.17.179
20 2026-08-26 06:05 639233202925983161
569 ms 210.167.17.179
19 2026-08-26 05:47 639233192644780696
3 ms 210.167.17.179
18 2026-08-26 05:30 639233182401183833
280 ms 210.167.17.179
17 2026-08-26 05:13 639233172074181051
818 ms 210.167.17.179
16 2026-08-26 04:56 639233161808421455
811 ms 210.167.17.179
15 2026-08-26 04:39 639233151357344052
572 ms 210.167.17.179
14 2026-08-26 04:22 639233141034116946
570 ms 210.167.17.179
13 2026-08-26 04:04 639233130828334142
281 ms 210.167.17.179
12 2026-08-26 03:47 639233120373450007
2297 ms 210.167.17.179
11 2026-08-26 03:30 639233110066216193
803 ms 210.167.17.179
10 2026-08-26 02:37 639233078065410564
3 ms 210.167.17.179
9 2026-08-26 02:19 639233067787457832
3 ms 210.167.17.179
8 2026-08-26 02:02 639233057501801162
659 ms 210.167.17.179
7 2026-08-26 01:45 639233047089431703
544 ms 210.167.17.179
6 2026-08-26 01:28 639233036754790688
540 ms 210.167.17.179
5 2026-08-26 01:11 639233026412602472
785 ms 210.167.17.179
4 2026-08-26 00:53 639233016064066127
570 ms 210.167.17.179
3 2026-08-26 00:36 639233005922655772
564 ms 210.167.17.179
2 2026-08-26 00:19 639232995672256907
579 ms 210.167.17.179
1 2026-08-26 00:02 639232985300872416
5 ms 210.167.17.179