DNS response history for ns02.yahoo.co.jp

ns02.yahoo.co.jp 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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 209 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 ns02.yahoo.co.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

209 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.216.255.228

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 ns02.yahoo.co.jp

Showing DNS history for 2026-08-24 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-24 15:15 639231807961539652
10 ms 203.216.255.228
35 2026-08-24 14:59 639231797631669865
277 ms 203.216.255.228
34 2026-08-24 14:06 639231765923559455
8 ms 203.216.255.228
33 2026-08-24 13:49 639231755868832964
295 ms 203.216.255.228
32 2026-08-24 13:32 639231745628278877
11 ms 203.216.255.228
31 2026-08-24 13:15 639231735407682062
283 ms 203.216.255.228
30 2026-08-24 12:22 639231703815441688
283 ms 203.216.255.228
29 2026-08-24 12:05 639231693747052549
286 ms 203.216.255.228
28 2026-08-24 11:48 639231683712487276
276 ms 203.216.255.228
27 2026-08-24 11:32 639231673513573868
289 ms 203.216.255.228
26 2026-08-24 10:38 639231641791249939
278 ms 203.216.255.228
25 2026-08-24 10:22 639231631866211033
552 ms 203.216.255.228
24 2026-08-24 10:05 639231621644955316
435 ms 203.216.255.228
23 2026-08-24 09:48 639231611478799259
12 ms 203.216.255.228
22 2026-08-24 08:56 639231579923718211
8 ms 203.216.255.228
21 2026-08-24 08:39 639231569810702936
15 ms 203.216.255.228
20 2026-08-24 08:22 639231559762411619
272 ms 203.216.255.228
19 2026-08-24 08:05 639231549663595407
280 ms 203.216.255.228
18 2026-08-24 07:12 639231518076817246
552 ms 203.216.255.228
17 2026-08-24 06:56 639231508078650885
275 ms 203.216.255.228
16 2026-08-24 06:39 639231498210697093
263 ms 203.216.255.228
15 2026-08-24 06:23 639231488109699360
274 ms 203.216.255.228
14 2026-08-24 05:30 639231456772510692
11 ms 203.216.255.228
13 2026-08-24 05:14 639231447084631185
7 ms 203.216.255.228
12 2026-08-24 04:58 639231437208519473
260 ms 203.216.255.228
11 2026-08-24 04:41 639231427209627490
292 ms 203.216.255.228
10 2026-08-24 03:49 639231395791246644
271 ms 203.216.255.228
9 2026-08-24 03:32 639231386075551458
25 ms 203.216.255.228
8 2026-08-24 03:16 639231376208713791
31 ms 203.216.255.228
7 2026-08-24 02:59 639231366170589276
245 ms 203.216.255.228
6 2026-08-24 02:07 639231334732159368
270 ms 203.216.255.228
5 2026-08-24 01:51 639231325035670078
557 ms 203.216.255.228
4 2026-08-24 01:34 639231315132253837
269 ms 203.216.255.228
3 2026-08-24 01:18 639231305014280808
13 ms 203.216.255.228
2 2026-08-24 00:25 639231273779380675
12 ms 203.216.255.228
1 2026-08-24 00:09 639231264180839154
33 ms 203.216.255.228