DNS response history for ns2.basicstyle.co.jp

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

37

Historical checks stored for this nameserver on selected date

Average Latency

460 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

153.123.7.210

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.basicstyle.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
37 2026-08-24 15:37 639231818080917481
3 ms 153.123.7.210
36 2026-08-24 15:20 639231807961539652
494 ms 153.123.7.210
35 2026-08-24 15:03 639231797631669865
1005 ms 153.123.7.210
34 2026-08-24 14:10 639231765923559455
781 ms 153.123.7.210
33 2026-08-24 13:53 639231755868832964
493 ms 153.123.7.210
32 2026-08-24 13:36 639231745628278877
4 ms 153.123.7.210
31 2026-08-24 13:19 639231735407682062
1249 ms 153.123.7.210
30 2026-08-24 12:26 639231703815441688
751 ms 153.123.7.210
29 2026-08-24 12:10 639231693747052549
488 ms 153.123.7.210
28 2026-08-24 11:53 639231683712487276
513 ms 153.123.7.210
27 2026-08-24 11:36 639231673513573868
1010 ms 153.123.7.210
26 2026-08-24 10:43 639231641791249939
2 ms 153.123.7.210
25 2026-08-24 10:26 639231631866211033
2284 ms 153.123.7.210
24 2026-08-24 10:10 639231621644955316
333 ms 153.123.7.210
23 2026-08-24 09:53 639231611478799259
3 ms 153.123.7.210
22 2026-08-24 09:00 639231579923718211
512 ms 153.123.7.210
21 2026-08-24 08:43 639231569810702936
535 ms 153.123.7.210
20 2026-08-24 08:26 639231559762411619
1009 ms 153.123.7.210
19 2026-08-24 08:10 639231549663595407
796 ms 153.123.7.210
18 2026-08-24 07:17 639231518076817246
3 ms 153.123.7.210
17 2026-08-24 07:00 639231508078650885
3 ms 153.123.7.210
16 2026-08-24 06:44 639231498210697093
515 ms 153.123.7.210
15 2026-08-24 06:27 639231488109699360
3 ms 153.123.7.210
14 2026-08-24 05:35 639231456772510692
3 ms 153.123.7.210
13 2026-08-24 05:18 639231447084631185
3 ms 153.123.7.210
12 2026-08-24 05:02 639231437208519473
2 ms 153.123.7.210
11 2026-08-24 04:45 639231427209627490
1287 ms 153.123.7.210
10 2026-08-24 03:53 639231395791246644
2 ms 153.123.7.210
9 2026-08-24 03:37 639231386075551458
508 ms 153.123.7.210
8 2026-08-24 03:20 639231376208713791
492 ms 153.123.7.210
7 2026-08-24 03:04 639231366170589276
891 ms 153.123.7.210
6 2026-08-24 02:11 639231334732159368
2 ms 153.123.7.210
5 2026-08-24 01:55 639231325035670078
2 ms 153.123.7.210
4 2026-08-24 01:39 639231315132253837
9 ms 153.123.7.210
3 2026-08-24 01:22 639231305014280808
3 ms 153.123.7.210
2 2026-08-24 00:29 639231273779380675
1006 ms 153.123.7.210
1 2026-08-24 00:13 639231264180839154
3 ms 153.123.7.210