If you are not receiving API responses for some vessels in your fleets, consider these common causes and their solutions:
1. Incorrect or Missing timespan Parameter
The API only includes vessels whose information was received within the defined timespan.
If timespan is not explicitly defined, the default value is used, which may not cover the required period.
If the timespan value is too small, data for vessels that reported outside this interval will be excluded.
Solution:
Ensure the timespan parameter is correctly defined in your API call.
Example:
/timespan:30/
This retrieves data from the last 30 minutes.
2. Limited Coverage in Certain Areas
Some vessels in your fleets may be operating in regions with limited AIS coverage, such as:
Remote areas with sparse terrestrial AIS stations.
Regions where satellite AIS reception is unavailable or delayed.
Areas with poor connectivity due to roaming or environmental factors.
Explanation:
This behavior is expected for vessels in such regions. The API will return new positions as soon as the vessels transmit them and the information is received.
Quick Troubleshooting Checklist
Verify the timespan value: Ensure it is set correctly to capture recent AIS messages.
Understand coverage limitations: Recognize that delayed responses are expected for vessels in areas with limited AIS reception.
For further assistance or detailed diagnostics, consult the API documentation or contact support.