DNS response history for ns2.yamosta.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

70 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

70.40.138.19

Most recently resolved hosting IP on selected date

Successful Responses

37

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.yamosta.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
37 2026-08-25 12:42 639232576780683689
79 ms 70.40.138.19
36 2026-08-25 12:25 639232566381512620
4 ms 70.40.138.19
35 2026-08-25 12:07 639232556111768563
95 ms 70.40.138.19
34 2026-08-25 11:50 639232545839529039
5 ms 70.40.138.19
33 2026-08-25 11:33 639232535349285207
82 ms 70.40.138.19
32 2026-08-25 11:15 639232524938080723
43 ms 70.40.138.19
31 2026-08-25 10:22 639232492740373468
82 ms 70.40.138.19
30 2026-08-25 10:05 639232482235303141
85 ms 70.40.138.19
29 2026-08-25 09:47 639232471861770303
109 ms 70.40.138.19
28 2026-08-25 09:30 639232461630217327
80 ms 70.40.138.19
27 2026-08-25 09:13 639232451282965990
84 ms 70.40.138.19
26 2026-08-25 08:55 639232440814614938
90 ms 70.40.138.19
25 2026-08-25 08:38 639232430410720425
5 ms 70.40.138.19
24 2026-08-25 08:21 639232420003096185
89 ms 70.40.138.19
23 2026-08-25 08:03 639232409467287444
82 ms 70.40.138.19
22 2026-08-25 07:46 639232399077195997
80 ms 70.40.138.19
21 2026-08-25 07:28 639232388731528337
40 ms 70.40.138.19
20 2026-08-25 07:11 639232378288598612
106 ms 70.40.138.19
19 2026-08-25 06:17 639232346196373643
85 ms 70.40.138.19
18 2026-08-25 06:00 639232336112370741
84 ms 70.40.138.19
17 2026-08-25 05:44 639232326146508970
41 ms 70.40.138.19
16 2026-08-25 05:27 639232316189381720
42 ms 70.40.138.19
15 2026-08-25 05:11 639232306217998913
82 ms 70.40.138.19
14 2026-08-25 04:54 639232296255744174
3 ms 70.40.138.19
13 2026-08-25 04:37 639232286095760789
81 ms 70.40.138.19
12 2026-08-25 04:20 639232276086186273
43 ms 70.40.138.19
11 2026-08-25 04:03 639232265900986425
42 ms 70.40.138.19
10 2026-08-25 03:47 639232255723518075
81 ms 70.40.138.19
9 2026-08-25 03:30 639232245484452890
87 ms 70.40.138.19
8 2026-08-25 03:12 639232235157175331
80 ms 70.40.138.19
7 2026-08-25 02:19 639232203197189095
76 ms 70.40.138.19
6 2026-08-25 02:02 639232192844564298
81 ms 70.40.138.19
5 2026-08-25 01:45 639232182496008942
80 ms 70.40.138.19
4 2026-08-25 01:27 639232172197053132
131 ms 70.40.138.19
3 2026-08-25 00:34 639232140250307418
44 ms 70.40.138.19
2 2026-08-25 00:17 639232129927860324
85 ms 70.40.138.19
1 2026-08-25 00:00 639232119551972438
85 ms 70.40.138.19