DNS response history for ns2.yamamura-clinic.net

ns2.yamamura-clinic.net 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 34 DNS check records, 34 successful responses, 0 failed responses, and 803 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.yamamura-clinic.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

803 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.241.129.62

Most recently resolved hosting IP on selected date

Successful Responses

34

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.yamamura-clinic.net

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
34 2026-08-25 11:51 639232545839529039
1095 ms 103.241.129.62
33 2026-08-25 11:34 639232535349285207
1081 ms 103.241.129.62
32 2026-08-25 11:16 639232524938080723
918 ms 103.241.129.62
31 2026-08-25 10:22 639232492740373468
1084 ms 103.241.129.62
30 2026-08-25 10:05 639232482235303141
1081 ms 103.241.129.62
29 2026-08-25 09:48 639232471861770303
1085 ms 103.241.129.62
28 2026-08-25 09:31 639232461630217327
1085 ms 103.241.129.62
27 2026-08-25 09:13 639232451282965990
521 ms 103.241.129.62
26 2026-08-25 08:56 639232440814614938
500 ms 103.241.129.62
25 2026-08-25 08:39 639232430410720425
1099 ms 103.241.129.62
24 2026-08-25 08:21 639232420003096185
510 ms 103.241.129.62
23 2026-08-25 08:04 639232409467287444
497 ms 103.241.129.62
22 2026-08-25 07:47 639232399077195997
1088 ms 103.241.129.62
21 2026-08-25 07:29 639232388731528337
503 ms 103.241.129.62
20 2026-08-25 07:12 639232378288598612
520 ms 103.241.129.62
19 2026-08-25 06:18 639232346196373643
1082 ms 103.241.129.62
18 2026-08-25 06:01 639232336112370741
986 ms 103.241.129.62
17 2026-08-25 05:44 639232326146508970
1093 ms 103.241.129.62
16 2026-08-25 05:28 639232316189381720
1098 ms 103.241.129.62
15 2026-08-25 05:11 639232306217998913
518 ms 103.241.129.62
14 2026-08-25 04:55 639232296255744174
501 ms 103.241.129.62
13 2026-08-25 04:38 639232286095760789
1079 ms 103.241.129.62
12 2026-08-25 04:21 639232276086186273
372 ms 103.241.129.62
11 2026-08-25 04:04 639232265900986425
1091 ms 103.241.129.62
10 2026-08-25 03:47 639232255723518075
513 ms 103.241.129.62
9 2026-08-25 03:30 639232245484452890
503 ms 103.241.129.62
8 2026-08-25 03:13 639232235157175331
1087 ms 103.241.129.62
7 2026-08-25 02:20 639232203197189095
516 ms 103.241.129.62
6 2026-08-25 02:03 639232192844564298
1086 ms 103.241.129.62
5 2026-08-25 01:46 639232182496008942
1096 ms 103.241.129.62
4 2026-08-25 01:28 639232172197053132
507 ms 103.241.129.62
3 2026-08-25 00:35 639232140250307418
514 ms 103.241.129.62
2 2026-08-25 00:18 639232129927860324
505 ms 103.241.129.62
1 2026-08-25 00:01 639232119551972438
503 ms 103.241.129.62