DNS response history for ns1.aikome.com

ns1.aikome.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 27 DNS check records, 27 successful responses, 0 failed responses, and 472 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.aikome.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

472 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

35.186.151.61

Most recently resolved hosting IP on selected date

Successful Responses

27

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.aikome.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
27 2026-08-26 08:43 639233297961740122
564 ms 35.186.151.61
26 2026-08-26 08:26 639233287487159094
571 ms 35.186.151.61
25 2026-08-26 08:08 639233276995531707
571 ms 35.186.151.61
24 2026-08-26 07:51 639233266521568229
289 ms 35.186.151.61
23 2026-08-26 07:33 639233256081047431
576 ms 35.186.151.61
22 2026-08-26 06:39 639233223620132921
3 ms 35.186.151.61
21 2026-08-26 06:22 639233213287814244
566 ms 35.186.151.61
20 2026-08-26 06:05 639233202925983161
4 ms 35.186.151.61
19 2026-08-26 05:47 639233192644780696
563 ms 35.186.151.61
18 2026-08-26 05:30 639233182401183833
4 ms 35.186.151.61
17 2026-08-26 05:13 639233172074181051
283 ms 35.186.151.61
16 2026-08-26 04:56 639233161808421455
565 ms 35.186.151.61
15 2026-08-26 04:39 639233151357344052
557 ms 35.186.151.61
14 2026-08-26 04:21 639233141034116946
569 ms 35.186.151.61
13 2026-08-26 04:04 639233130828334142
3 ms 35.186.151.61
12 2026-08-26 03:47 639233120373450007
563 ms 35.186.151.61
11 2026-08-26 03:30 639233110066216193
889 ms 35.186.151.61
10 2026-08-26 02:37 639233078065410564
560 ms 35.186.151.61
9 2026-08-26 02:19 639233067787457832
563 ms 35.186.151.61
8 2026-08-26 02:02 639233057501801162
561 ms 35.186.151.61
7 2026-08-26 01:45 639233047089431703
558 ms 35.186.151.61
6 2026-08-26 01:28 639233036754790688
555 ms 35.186.151.61
5 2026-08-26 01:11 639233026412602472
555 ms 35.186.151.61
4 2026-08-26 00:53 639233016064066127
572 ms 35.186.151.61
3 2026-08-26 00:36 639233005922655772
554 ms 35.186.151.61
2 2026-08-26 00:19 639232995672256907
561 ms 35.186.151.61
1 2026-08-26 00:02 639232985300872416
555 ms 35.186.151.61