DNS response history for ns.shrine.kyoto.jp

ns.shrine.kyoto.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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 720 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 ns.shrine.kyoto.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

720 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.16.222.162

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns.shrine.kyoto.jp

Showing DNS history for 2026-08-26 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
28 2026-08-26 09:01 639233308387917838
620 ms 160.16.222.162
27 2026-08-26 08:44 639233297961740122
596 ms 160.16.222.162
26 2026-08-26 08:27 639233287487159094
565 ms 160.16.222.162
25 2026-08-26 08:09 639233276995531707
575 ms 160.16.222.162
24 2026-08-26 07:52 639233266521568229
789 ms 160.16.222.162
23 2026-08-26 07:34 639233256081047431
581 ms 160.16.222.162
22 2026-08-26 06:40 639233223620132921
786 ms 160.16.222.162
21 2026-08-26 06:23 639233213287814244
797 ms 160.16.222.162
20 2026-08-26 06:05 639233202925983161
1004 ms 160.16.222.162
19 2026-08-26 05:48 639233192644780696
1068 ms 160.16.222.162
18 2026-08-26 05:31 639233182401183833
797 ms 160.16.222.162
17 2026-08-26 05:14 639233172074181051
573 ms 160.16.222.162
16 2026-08-26 04:57 639233161808421455
833 ms 160.16.222.162
15 2026-08-26 04:40 639233151357344052
773 ms 160.16.222.162
14 2026-08-26 04:22 639233141034116946
1040 ms 160.16.222.162
13 2026-08-26 04:05 639233130828334142
773 ms 160.16.222.162
12 2026-08-26 03:48 639233120373450007
584 ms 160.16.222.162
11 2026-08-26 03:31 639233110066216193
772 ms 160.16.222.162
10 2026-08-26 02:37 639233078065410564
750 ms 160.16.222.162
9 2026-08-26 02:20 639233067787457832
751 ms 160.16.222.162
8 2026-08-26 02:03 639233057501801162
586 ms 160.16.222.162
7 2026-08-26 01:46 639233047089431703
568 ms 160.16.222.162
6 2026-08-26 01:29 639233036754790688
768 ms 160.16.222.162
5 2026-08-26 01:11 639233026412602472
578 ms 160.16.222.162
4 2026-08-26 00:54 639233016064066127
773 ms 160.16.222.162
3 2026-08-26 00:37 639233005922655772
783 ms 160.16.222.162
2 2026-08-26 00:20 639232995672256907
765 ms 160.16.222.162
1 2026-08-26 00:03 639232985300872416
301 ms 160.16.222.162