DNS response history for ns4.kenko-tokyo.com

ns4.kenko-tokyo.com 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 25 DNS check records, 25 successful responses, 0 failed responses, and 344 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 ns4.kenko-tokyo.com.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

152.160.227.63

Most recently resolved hosting IP on selected date

Successful Responses

25

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 ns4.kenko-tokyo.com

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
25 2026-08-26 08:23 639233287487159094
161 ms 152.160.227.63
24 2026-08-26 08:05 639233276995531707
225 ms 152.160.227.63
23 2026-08-26 07:48 639233266521568229
9 ms 152.160.227.63
22 2026-08-26 07:30 639233256081047431
224 ms 152.160.227.63
21 2026-08-26 06:36 639233223620132921
245 ms 152.160.227.63
20 2026-08-26 06:19 639233213287814244
2127 ms 152.160.227.63
19 2026-08-26 06:02 639233202925983161
239 ms 152.160.227.63
18 2026-08-26 05:44 639233192644780696
231 ms 152.160.227.63
17 2026-08-26 05:27 639233182401183833
112 ms 152.160.227.63
16 2026-08-26 05:10 639233172074181051
2172 ms 152.160.227.63
15 2026-08-26 04:53 639233161808421455
240 ms 152.160.227.63
14 2026-08-26 04:36 639233151357344052
150 ms 152.160.227.63
13 2026-08-26 04:18 639233141034116946
134 ms 152.160.227.63
12 2026-08-26 04:01 639233130828334142
231 ms 152.160.227.63
11 2026-08-26 03:44 639233120373450007
115 ms 152.160.227.63
10 2026-08-26 03:27 639233110066216193
241 ms 152.160.227.63
9 2026-08-26 02:33 639233078065410564
224 ms 152.160.227.63
8 2026-08-26 02:16 639233067787457832
114 ms 152.160.227.63
7 2026-08-26 01:59 639233057501801162
226 ms 152.160.227.63
6 2026-08-26 01:42 639233047089431703
242 ms 152.160.227.63
5 2026-08-26 01:25 639233036754790688
226 ms 152.160.227.63
4 2026-08-26 01:08 639233026412602472
229 ms 152.160.227.63
3 2026-08-26 00:50 639233016064066127
244 ms 152.160.227.63
2 2026-08-26 00:33 639233005922655772
7 ms 152.160.227.63
1 2026-08-26 00:16 639232995672256907
230 ms 152.160.227.63