DNS response history for ns2.baobab.or.jp

ns2.baobab.or.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 37 DNS check records, 37 successful responses, 0 failed responses, and 408 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.baobab.or.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.157.233.9

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.baobab.or.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
37 2026-08-24 15:37 639231818080917481
6 ms 210.157.233.9
36 2026-08-24 15:20 639231807961539652
548 ms 210.157.233.9
35 2026-08-24 15:03 639231797631669865
667 ms 210.157.233.9
34 2026-08-24 14:10 639231765923559455
4 ms 210.157.233.9
33 2026-08-24 13:53 639231755868832964
531 ms 210.157.233.9
32 2026-08-24 13:36 639231745628278877
564 ms 210.157.233.9
31 2026-08-24 13:19 639231735407682062
555 ms 210.157.233.9
30 2026-08-24 12:26 639231703815441688
555 ms 210.157.233.9
29 2026-08-24 12:10 639231693747052549
593 ms 210.157.233.9
28 2026-08-24 11:53 639231683712487276
565 ms 210.157.233.9
27 2026-08-24 11:36 639231673513573868
565 ms 210.157.233.9
26 2026-08-24 10:43 639231641791249939
4 ms 210.157.233.9
25 2026-08-24 10:26 639231631866211033
4 ms 210.157.233.9
24 2026-08-24 10:10 639231621644955316
587 ms 210.157.233.9
23 2026-08-24 09:53 639231611478799259
556 ms 210.157.233.9
22 2026-08-24 09:00 639231579923718211
561 ms 210.157.233.9
21 2026-08-24 08:43 639231569810702936
558 ms 210.157.233.9
20 2026-08-24 08:26 639231559762411619
319 ms 210.157.233.9
19 2026-08-24 08:09 639231549663595407
563 ms 210.157.233.9
18 2026-08-24 07:17 639231518076817246
310 ms 210.157.233.9
17 2026-08-24 07:00 639231508078650885
575 ms 210.157.233.9
16 2026-08-24 06:44 639231498210697093
592 ms 210.157.233.9
15 2026-08-24 06:27 639231488109699360
566 ms 210.157.233.9
14 2026-08-24 05:35 639231456772510692
536 ms 210.157.233.9
13 2026-08-24 05:18 639231447084631185
3 ms 210.157.233.9
12 2026-08-24 05:02 639231437208519473
473 ms 210.157.233.9
11 2026-08-24 04:45 639231427209627490
567 ms 210.157.233.9
10 2026-08-24 03:53 639231395791246644
3 ms 210.157.233.9
9 2026-08-24 03:37 639231386075551458
312 ms 210.157.233.9
8 2026-08-24 03:20 639231376208713791
603 ms 210.157.233.9
7 2026-08-24 03:04 639231366170589276
554 ms 210.157.233.9
6 2026-08-24 02:11 639231334732159368
3 ms 210.157.233.9
5 2026-08-24 01:55 639231325035670078
3 ms 210.157.233.9
4 2026-08-24 01:39 639231315132253837
570 ms 210.157.233.9
3 2026-08-24 01:22 639231305014280808
3 ms 210.157.233.9
2 2026-08-24 00:29 639231273779380675
554 ms 210.157.233.9
1 2026-08-24 00:13 639231264180839154
565 ms 210.157.233.9