DNS response history for ns2.yamablo.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

366 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.135.255.201

Most recently resolved hosting IP on selected date

Successful Responses

30

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.yamablo.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
30 2026-08-25 10:13 639232492740373468
34 ms 147.135.255.201
29 2026-08-25 09:55 639232482235303141
37 ms 147.135.255.201
28 2026-08-25 09:38 639232471861770303
5 ms 147.135.255.201
27 2026-08-25 09:21 639232461630217327
2042 ms 147.135.255.201
26 2026-08-25 09:04 639232451282965990
28 ms 147.135.255.201
25 2026-08-25 08:46 639232440814614938
6 ms 147.135.255.201
24 2026-08-25 08:29 639232430410720425
40 ms 147.135.255.201
23 2026-08-25 08:12 639232420003096185
41 ms 147.135.255.201
22 2026-08-25 07:54 639232409467287444
38 ms 147.135.255.201
21 2026-08-25 07:37 639232399077195997
41 ms 147.135.255.201
20 2026-08-25 07:19 639232388731528337
2074 ms 147.135.255.201
19 2026-08-25 07:02 639232378288598612
19 ms 147.135.255.201
18 2026-08-25 06:08 639232346196373643
17 ms 147.135.255.201
17 2026-08-25 05:52 639232336112370741
2011 ms 147.135.255.201
16 2026-08-25 05:35 639232326146508970
6 ms 147.135.255.201
15 2026-08-25 05:18 639232316189381720
29 ms 147.135.255.201
14 2026-08-25 05:02 639232306217998913
4047 ms 147.135.255.201
13 2026-08-25 04:45 639232296255744174
39 ms 147.135.255.201
12 2026-08-25 04:28 639232286095760789
2 ms 147.135.255.201
11 2026-08-25 04:12 639232276086186273
26 ms 147.135.255.201
10 2026-08-25 03:55 639232265900986425
41 ms 147.135.255.201
9 2026-08-25 03:38 639232255723518075
35 ms 147.135.255.201
8 2026-08-25 03:21 639232245484452890
38 ms 147.135.255.201
7 2026-08-25 03:03 639232235157175331
82 ms 147.135.255.201
6 2026-08-25 02:10 639232203197189095
38 ms 147.135.255.201
5 2026-08-25 01:53 639232192844564298
8 ms 147.135.255.201
4 2026-08-25 01:36 639232182496008942
32 ms 147.135.255.201
3 2026-08-25 01:18 639232172197053132
33 ms 147.135.255.201
2 2026-08-25 00:25 639232140250307418
41 ms 147.135.255.201
1 2026-08-25 00:08 639232129927860324
60 ms 147.135.255.201