DNS response history for ns1.takt.co.jp

ns1.takt.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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 499 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.takt.co.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

499 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.160.102.210

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 ns1.takt.co.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:00 639233308387917838
378 ms 210.160.102.210
27 2026-08-26 08:43 639233297961740122
285 ms 210.160.102.210
26 2026-08-26 08:26 639233287487159094
282 ms 210.160.102.210
25 2026-08-26 08:08 639233276995531707
281 ms 210.160.102.210
24 2026-08-26 07:51 639233266521568229
338 ms 210.160.102.210
23 2026-08-26 07:33 639233256081047431
570 ms 210.160.102.210
22 2026-08-26 06:39 639233223620132921
539 ms 210.160.102.210
21 2026-08-26 06:22 639233213287814244
558 ms 210.160.102.210
20 2026-08-26 06:05 639233202925983161
270 ms 210.160.102.210
19 2026-08-26 05:47 639233192644780696
561 ms 210.160.102.210
18 2026-08-26 05:30 639233182401183833
291 ms 210.160.102.210
17 2026-08-26 05:13 639233172074181051
289 ms 210.160.102.210
16 2026-08-26 04:56 639233161808421455
552 ms 210.160.102.210
15 2026-08-26 04:39 639233151357344052
527 ms 210.160.102.210
14 2026-08-26 04:22 639233141034116946
795 ms 210.160.102.210
13 2026-08-26 04:04 639233130828334142
276 ms 210.160.102.210
12 2026-08-26 03:47 639233120373450007
541 ms 210.160.102.210
11 2026-08-26 03:30 639233110066216193
536 ms 210.160.102.210
10 2026-08-26 02:37 639233078065410564
550 ms 210.160.102.210
9 2026-08-26 02:19 639233067787457832
286 ms 210.160.102.210
8 2026-08-26 02:02 639233057501801162
295 ms 210.160.102.210
7 2026-08-26 01:45 639233047089431703
525 ms 210.160.102.210
6 2026-08-26 01:28 639233036754790688
519 ms 210.160.102.210
5 2026-08-26 01:11 639233026412602472
2291 ms 210.160.102.210
4 2026-08-26 00:53 639233016064066127
291 ms 210.160.102.210
3 2026-08-26 00:36 639233005922655772
292 ms 210.160.102.210
2 2026-08-26 00:19 639232995672256907
781 ms 210.160.102.210
1 2026-08-26 00:02 639232985300872416
285 ms 210.160.102.210