DNS response history for ns1.ahanapp.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

302 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.170.49.43

Most recently resolved hosting IP on selected date

Successful Responses

34

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.ahanapp.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
34 2026-08-26 10:43 639233370841350248
257 ms 31.170.49.43
33 2026-08-26 10:25 639233360361507238
334 ms 31.170.49.43
32 2026-08-26 10:08 639233350067824371
352 ms 31.170.49.43
31 2026-08-26 09:51 639233339545274518
232 ms 31.170.49.43
30 2026-08-26 09:33 639233329214918079
215 ms 31.170.49.43
29 2026-08-26 09:16 639233318749762337
249 ms 31.170.49.43
28 2026-08-26 08:59 639233308387917838
260 ms 31.170.49.43
27 2026-08-26 08:41 639233297961740122
219 ms 31.170.49.43
26 2026-08-26 08:24 639233287487159094
239 ms 31.170.49.43
25 2026-08-26 08:07 639233276995531707
243 ms 31.170.49.43
24 2026-08-26 07:49 639233266521568229
258 ms 31.170.49.43
23 2026-08-26 07:31 639233256081047431
257 ms 31.170.49.43
22 2026-08-26 06:38 639233223620132921
271 ms 31.170.49.43
21 2026-08-26 06:20 639233213287814244
225 ms 31.170.49.43
20 2026-08-26 06:03 639233202925983161
256 ms 31.170.49.43
19 2026-08-26 05:46 639233192644780696
242 ms 31.170.49.43
18 2026-08-26 05:28 639233182401183833
286 ms 31.170.49.43
17 2026-08-26 05:12 639233172074181051
3 ms 31.170.49.43
16 2026-08-26 04:54 639233161808421455
231 ms 31.170.49.43
15 2026-08-26 04:37 639233151357344052
227 ms 31.170.49.43
14 2026-08-26 04:20 639233141034116946
453 ms 31.170.49.43
13 2026-08-26 04:03 639233130828334142
218 ms 31.170.49.43
12 2026-08-26 03:45 639233120373450007
235 ms 31.170.49.43
11 2026-08-26 03:28 639233110066216193
239 ms 31.170.49.43
10 2026-08-26 02:35 639233078065410564
2159 ms 31.170.49.43
9 2026-08-26 02:18 639233067787457832
234 ms 31.170.49.43
8 2026-08-26 02:00 639233057501801162
232 ms 31.170.49.43
7 2026-08-26 01:43 639233047089431703
233 ms 31.170.49.43
6 2026-08-26 01:26 639233036754790688
225 ms 31.170.49.43
5 2026-08-26 01:09 639233026412602472
249 ms 31.170.49.43
4 2026-08-26 00:51 639233016064066127
233 ms 31.170.49.43
3 2026-08-26 00:34 639233005922655772
255 ms 31.170.49.43
2 2026-08-26 00:17 639232995672256907
219 ms 31.170.49.43
1 2026-08-26 00:00 639232985300872416
220 ms 31.170.49.43