DNS response history for ns1.n-syakyo.jp

ns1.n-syakyo.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 30 DNS check records, 30 successful responses, 0 failed responses, and 364 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 ns1.n-syakyo.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

364 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.169.126.231

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 ns1.n-syakyo.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
30 2026-08-24 12:26 639231703815441688
3 ms 59.169.126.231
29 2026-08-24 12:10 639231693747052549
5 ms 59.169.126.231
28 2026-08-24 11:53 639231683712487276
516 ms 59.169.126.231
27 2026-08-24 11:36 639231673513573868
552 ms 59.169.126.231
26 2026-08-24 10:43 639231641791249939
572 ms 59.169.126.231
25 2026-08-24 10:26 639231631866211033
5 ms 59.169.126.231
24 2026-08-24 10:10 639231621644955316
533 ms 59.169.126.231
23 2026-08-24 09:53 639231611478799259
548 ms 59.169.126.231
22 2026-08-24 09:00 639231579923718211
542 ms 59.169.126.231
21 2026-08-24 08:43 639231569810702936
539 ms 59.169.126.231
20 2026-08-24 08:26 639231559762411619
377 ms 59.169.126.231
19 2026-08-24 08:10 639231549663595407
531 ms 59.169.126.231
18 2026-08-24 07:17 639231518076817246
3 ms 59.169.126.231
17 2026-08-24 07:00 639231508078650885
2 ms 59.169.126.231
16 2026-08-24 06:44 639231498210697093
563 ms 59.169.126.231
15 2026-08-24 06:27 639231488109699360
545 ms 59.169.126.231
14 2026-08-24 05:35 639231456772510692
4 ms 59.169.126.231
13 2026-08-24 05:18 639231447084631185
535 ms 59.169.126.231
12 2026-08-24 05:02 639231437208519473
351 ms 59.169.126.231
11 2026-08-24 04:45 639231427209627490
4 ms 59.169.126.231
10 2026-08-24 03:53 639231395791246644
536 ms 59.169.126.231
9 2026-08-24 03:37 639231386075551458
550 ms 59.169.126.231
8 2026-08-24 03:20 639231376208713791
3 ms 59.169.126.231
7 2026-08-24 03:04 639231366170589276
561 ms 59.169.126.231
6 2026-08-24 02:11 639231334732159368
309 ms 59.169.126.231
5 2026-08-24 01:55 639231325035670078
308 ms 59.169.126.231
4 2026-08-24 01:39 639231315132253837
546 ms 59.169.126.231
3 2026-08-24 01:22 639231305014280808
547 ms 59.169.126.231
2 2026-08-24 00:29 639231273779380675
544 ms 59.169.126.231
1 2026-08-24 00:14 639231264180839154
274 ms 59.169.126.231