DNS response history for ns2.yamap.top

ns2.yamap.top 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 194 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.yamap.top.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

194 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

85.17.151.24

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 ns2.yamap.top

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:06 639232524938080723
63 ms 85.17.151.24
30 2026-08-25 10:13 639232492740373468
136 ms 85.17.151.24
29 2026-08-25 09:55 639232482235303141
19 ms 85.17.151.24
28 2026-08-25 09:38 639232471861770303
31 ms 85.17.151.24
27 2026-08-25 09:21 639232461630217327
54 ms 85.17.151.24
26 2026-08-25 09:04 639232451282965990
575 ms 85.17.151.24
25 2026-08-25 08:46 639232440814614938
59 ms 85.17.151.24
24 2026-08-25 08:29 639232430410720425
116 ms 85.17.151.24
23 2026-08-25 08:12 639232420003096185
34 ms 85.17.151.24
22 2026-08-25 07:54 639232409467287444
65 ms 85.17.151.24
21 2026-08-25 07:37 639232399077195997
9 ms 85.17.151.24
20 2026-08-25 07:19 639232388731528337
26 ms 85.17.151.24
19 2026-08-25 07:02 639232378288598612
65 ms 85.17.151.24
18 2026-08-25 06:08 639232346196373643
2092 ms 85.17.151.24
17 2026-08-25 05:52 639232336112370741
23 ms 85.17.151.24
16 2026-08-25 05:35 639232326146508970
9 ms 85.17.151.24
15 2026-08-25 05:18 639232316189381720
3 ms 85.17.151.24
14 2026-08-25 05:02 639232306217998913
33 ms 85.17.151.24
13 2026-08-25 04:45 639232296255744174
62 ms 85.17.151.24
12 2026-08-25 04:28 639232286095760789
58 ms 85.17.151.24
11 2026-08-25 04:12 639232276086186273
13 ms 85.17.151.24
10 2026-08-25 03:55 639232265900986425
38 ms 85.17.151.24
9 2026-08-25 03:38 639232255723518075
52 ms 85.17.151.24
8 2026-08-25 03:21 639232245484452890
2020 ms 85.17.151.24
7 2026-08-25 03:03 639232235157175331
55 ms 85.17.151.24
6 2026-08-25 02:10 639232203197189095
23 ms 85.17.151.24
5 2026-08-25 01:53 639232192844564298
30 ms 85.17.151.24
4 2026-08-25 01:36 639232182496008942
23 ms 85.17.151.24
3 2026-08-25 01:18 639232172197053132
79 ms 85.17.151.24
2 2026-08-25 00:25 639232140250307418
57 ms 85.17.151.24
1 2026-08-25 00:08 639232129927860324
93 ms 85.17.151.24