DNS response history for ns2.yamato-707.com

ns2.yamato-707.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 36 DNS check records, 36 successful responses, 0 failed responses, and 519 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.yamato-707.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

519 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.171.141.61

Most recently resolved hosting IP on selected date

Successful Responses

36

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.yamato-707.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
36 2026-08-25 12:42 639232576780683689
465 ms 210.171.141.61
35 2026-08-25 12:24 639232566381512620
472 ms 210.171.141.61
34 2026-08-25 12:07 639232556111768563
469 ms 210.171.141.61
33 2026-08-25 11:50 639232545839529039
466 ms 210.171.141.61
32 2026-08-25 11:33 639232535349285207
467 ms 210.171.141.61
31 2026-08-25 11:15 639232524938080723
464 ms 210.171.141.61
30 2026-08-25 10:21 639232492740373468
462 ms 210.171.141.61
29 2026-08-25 10:04 639232482235303141
465 ms 210.171.141.61
28 2026-08-25 09:47 639232471861770303
467 ms 210.171.141.61
27 2026-08-25 09:29 639232461630217327
466 ms 210.171.141.61
26 2026-08-25 09:12 639232451282965990
505 ms 210.171.141.61
25 2026-08-25 08:55 639232440814614938
475 ms 210.171.141.61
24 2026-08-25 08:38 639232430410720425
471 ms 210.171.141.61
23 2026-08-25 08:20 639232420003096185
470 ms 210.171.141.61
22 2026-08-25 08:03 639232409467287444
465 ms 210.171.141.61
21 2026-08-25 07:45 639232399077195997
479 ms 210.171.141.61
20 2026-08-25 07:28 639232388731528337
465 ms 210.171.141.61
19 2026-08-25 07:11 639232378288598612
464 ms 210.171.141.61
18 2026-08-25 06:17 639232346196373643
2263 ms 210.171.141.61
17 2026-08-25 06:00 639232336112370741
464 ms 210.171.141.61
16 2026-08-25 05:43 639232326146508970
482 ms 210.171.141.61
15 2026-08-25 05:27 639232316189381720
464 ms 210.171.141.61
14 2026-08-25 05:10 639232306217998913
474 ms 210.171.141.61
13 2026-08-25 04:54 639232296255744174
463 ms 210.171.141.61
12 2026-08-25 04:37 639232286095760789
484 ms 210.171.141.61
11 2026-08-25 04:20 639232276086186273
463 ms 210.171.141.61
10 2026-08-25 04:03 639232265900986425
464 ms 210.171.141.61
9 2026-08-25 03:46 639232255723518075
490 ms 210.171.141.61
8 2026-08-25 03:29 639232245484452890
468 ms 210.171.141.61
7 2026-08-25 03:12 639232235157175331
468 ms 210.171.141.61
6 2026-08-25 02:19 639232203197189095
463 ms 210.171.141.61
5 2026-08-25 02:02 639232192844564298
465 ms 210.171.141.61
4 2026-08-25 01:44 639232182496008942
465 ms 210.171.141.61
3 2026-08-25 01:27 639232172197053132
464 ms 210.171.141.61
2 2026-08-25 00:34 639232140250307418
475 ms 210.171.141.61
1 2026-08-25 00:17 639232129927860324
464 ms 210.171.141.61