DNS response history for ns3.ameetar.com

ns3.ameetar.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 38 DNS check records, 38 successful responses, 0 failed responses, and 661 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 ns3.ameetar.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

661 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.24.28

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns3.ameetar.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
38 2026-08-26 12:46 639233445367152284
358 ms 162.159.24.28
37 2026-08-26 12:28 639233434974187439
358 ms 162.159.24.28
36 2026-08-26 12:11 639233424567558554
375 ms 162.159.24.28
35 2026-08-26 11:54 639233414056832719
363 ms 162.159.24.28
34 2026-08-26 11:36 639233403515141099
364 ms 162.159.24.28
33 2026-08-26 10:41 639233370841350248
366 ms 162.159.24.28
32 2026-08-26 10:24 639233360361507238
358 ms 162.159.24.28
31 2026-08-26 10:07 639233350067824371
348 ms 162.159.24.28
30 2026-08-26 09:50 639233339545274518
2237 ms 162.159.24.28
29 2026-08-26 09:32 639233329214918079
4510 ms 162.159.24.28
28 2026-08-26 09:15 639233318749762337
622 ms 162.159.24.28
27 2026-08-26 08:57 639233308387917838
355 ms 162.159.24.28
26 2026-08-26 08:40 639233297961740122
363 ms 162.159.24.28
25 2026-08-26 08:23 639233287487159094
440 ms 162.159.24.28
24 2026-08-26 08:05 639233276995531707
369 ms 162.159.24.28
23 2026-08-26 07:48 639233266521568229
437 ms 162.159.24.28
22 2026-08-26 07:30 639233256081047431
341 ms 162.159.24.28
21 2026-08-26 06:36 639233223620132921
355 ms 162.159.24.28
20 2026-08-26 06:19 639233213287814244
2493 ms 162.159.24.28
19 2026-08-26 06:02 639233202925983161
350 ms 162.159.24.28
18 2026-08-26 05:44 639233192644780696
365 ms 162.159.24.28
17 2026-08-26 05:27 639233182401183833
365 ms 162.159.24.28
16 2026-08-26 05:10 639233172074181051
4426 ms 162.159.24.28
15 2026-08-26 04:53 639233161808421455
362 ms 162.159.24.28
14 2026-08-26 04:36 639233151357344052
341 ms 162.159.24.28
13 2026-08-26 04:18 639233141034116946
354 ms 162.159.24.28
12 2026-08-26 04:01 639233130828334142
352 ms 162.159.24.28
11 2026-08-26 03:44 639233120373450007
356 ms 162.159.24.28
10 2026-08-26 03:27 639233110066216193
394 ms 162.159.24.28
9 2026-08-26 02:33 639233078065410564
348 ms 162.159.24.28
8 2026-08-26 02:16 639233067787457832
346 ms 162.159.24.28
7 2026-08-26 01:59 639233057501801162
357 ms 162.159.24.28
6 2026-08-26 01:42 639233047089431703
420 ms 162.159.24.28
5 2026-08-26 01:25 639233036754790688
350 ms 162.159.24.28
4 2026-08-26 01:08 639233026412602472
2 ms 162.159.24.28
3 2026-08-26 00:50 639233016064066127
3 ms 162.159.24.28
2 2026-08-26 00:33 639233005922655772
217 ms 162.159.24.28
1 2026-08-26 00:16 639232995672256907
4 ms 162.159.24.28