DNS response history for ns2.yamagatan.com

ns2.yamagatan.com 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 32 DNS check records, 32 successful responses, 0 failed responses, and 385 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.yamagatan.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.210.185.165

Most recently resolved hosting IP on selected date

Successful Responses

32

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.yamagatan.com

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
32 2026-08-25 11:32 639232535349285207
291 ms 202.210.185.165
31 2026-08-25 11:14 639232524938080723
322 ms 202.210.185.165
30 2026-08-25 10:21 639232492740373468
476 ms 202.210.185.165
29 2026-08-25 10:04 639232482235303141
10 ms 202.210.185.165
28 2026-08-25 09:46 639232471861770303
242 ms 202.210.185.165
27 2026-08-25 09:29 639232461630217327
261 ms 202.210.185.165
26 2026-08-25 09:12 639232451282965990
280 ms 202.210.185.165
25 2026-08-25 08:54 639232440814614938
248 ms 202.210.185.165
24 2026-08-25 08:37 639232430410720425
475 ms 202.210.185.165
23 2026-08-25 08:20 639232420003096185
288 ms 202.210.185.165
22 2026-08-25 08:02 639232409467287444
499 ms 202.210.185.165
21 2026-08-25 07:45 639232399077195997
246 ms 202.210.185.165
20 2026-08-25 07:27 639232388731528337
577 ms 202.210.185.165
19 2026-08-25 07:10 639232378288598612
246 ms 202.210.185.165
18 2026-08-25 06:16 639232346196373643
268 ms 202.210.185.165
17 2026-08-25 05:59 639232336112370741
487 ms 202.210.185.165
16 2026-08-25 05:43 639232326146508970
503 ms 202.210.185.165
15 2026-08-25 05:26 639232316189381720
483 ms 202.210.185.165
14 2026-08-25 05:10 639232306217998913
275 ms 202.210.185.165
13 2026-08-25 04:53 639232296255744174
468 ms 202.210.185.165
12 2026-08-25 04:36 639232286095760789
7 ms 202.210.185.165
11 2026-08-25 04:19 639232276086186273
479 ms 202.210.185.165
10 2026-08-25 04:03 639232265900986425
2010 ms 202.210.185.165
9 2026-08-25 03:46 639232255723518075
3 ms 202.210.185.165
8 2026-08-25 03:29 639232245484452890
240 ms 202.210.185.165
7 2026-08-25 03:11 639232235157175331
246 ms 202.210.185.165
6 2026-08-25 02:18 639232203197189095
237 ms 202.210.185.165
5 2026-08-25 02:01 639232192844564298
481 ms 202.210.185.165
4 2026-08-25 01:44 639232182496008942
480 ms 202.210.185.165
3 2026-08-25 01:26 639232172197053132
478 ms 202.210.185.165
2 2026-08-25 00:33 639232140250307418
477 ms 202.210.185.165
1 2026-08-25 00:16 639232129927860324
248 ms 202.210.185.165