DNS response history for ns2.hankomaturi.com

ns2.hankomaturi.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 37 DNS check records, 37 successful responses, 0 failed responses, and 530 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 ns2.hankomaturi.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

530 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.152.151.45

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2.hankomaturi.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
37 2026-08-26 12:14 639233424567558554
516 ms 210.152.151.45
36 2026-08-26 11:57 639233414056832719
514 ms 210.152.151.45
35 2026-08-26 11:39 639233403515141099
509 ms 210.152.151.45
34 2026-08-26 10:44 639233370841350248
497 ms 210.152.151.45
33 2026-08-26 10:27 639233360361507238
511 ms 210.152.151.45
32 2026-08-26 10:10 639233350067824371
508 ms 210.152.151.45
31 2026-08-26 09:53 639233339545274518
506 ms 210.152.151.45
30 2026-08-26 09:35 639233329214918079
499 ms 210.152.151.45
29 2026-08-26 09:18 639233318749762337
502 ms 210.152.151.45
28 2026-08-26 09:00 639233308387917838
328 ms 210.152.151.45
27 2026-08-26 08:43 639233297961740122
495 ms 210.152.151.45
26 2026-08-26 08:26 639233287487159094
509 ms 210.152.151.45
25 2026-08-26 08:08 639233276995531707
500 ms 210.152.151.45
24 2026-08-26 07:51 639233266521568229
506 ms 210.152.151.45
23 2026-08-26 07:33 639233256081047431
512 ms 210.152.151.45
22 2026-08-26 06:39 639233223620132921
506 ms 210.152.151.45
21 2026-08-26 06:22 639233213287814244
499 ms 210.152.151.45
20 2026-08-26 06:05 639233202925983161
502 ms 210.152.151.45
19 2026-08-26 05:47 639233192644780696
517 ms 210.152.151.45
18 2026-08-26 05:30 639233182401183833
515 ms 210.152.151.45
17 2026-08-26 05:13 639233172074181051
514 ms 210.152.151.45
16 2026-08-26 04:56 639233161808421455
506 ms 210.152.151.45
15 2026-08-26 04:39 639233151357344052
4 ms 210.152.151.45
14 2026-08-26 04:21 639233141034116946
513 ms 210.152.151.45
13 2026-08-26 04:04 639233130828334142
508 ms 210.152.151.45
12 2026-08-26 03:47 639233120373450007
509 ms 210.152.151.45
11 2026-08-26 03:30 639233110066216193
508 ms 210.152.151.45
10 2026-08-26 02:37 639233078065410564
307 ms 210.152.151.45
9 2026-08-26 02:19 639233067787457832
503 ms 210.152.151.45
8 2026-08-26 02:02 639233057501801162
2278 ms 210.152.151.45
7 2026-08-26 01:45 639233047089431703
494 ms 210.152.151.45
6 2026-08-26 01:28 639233036754790688
500 ms 210.152.151.45
5 2026-08-26 01:11 639233026412602472
512 ms 210.152.151.45
4 2026-08-26 00:53 639233016064066127
505 ms 210.152.151.45
3 2026-08-26 00:36 639233005922655772
506 ms 210.152.151.45
2 2026-08-26 00:19 639232995672256907
503 ms 210.152.151.45
1 2026-08-26 00:02 639232985300872416
494 ms 210.152.151.45