AISHub · Rate Limits

Aishub Rate Limits

AISHub publishes one explicit rate limit for its HTTP web service - do not access it more frequently than once per minute. The documentation states the web service simply returns nothing (an empty response) when called more often, rather than returning an HTTP throttling status. Beyond that polling cadence there are no documented per-day quotas or volume caps; large result sets are managed through bounding box, MMSI/IMO, and interval filters plus optional ZIP/GZIP/BZIP2 compression. Continued API access is additionally conditioned on your contributed feed maintaining its quality thresholds (10+ vessels coverage, 90%+ uptime over a rolling 7-day period, message delay under 10 seconds).

Aishub Rate Limits is the machine-readable rate-limit profile for AISHub on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, records, and feed quality.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Vessel Tracking, Maritime, AIS, Rate Limiting, and Quotas.

3 Limits Throttle: none documented (empty response body is returned instead)
Vessel TrackingMaritimeAISRate LimitingQuotas

Limits

Web Service Polling account
requests
1 per minute
Documented limit for ws.php and stations.php - the service returns nothing if executed more frequently than once per minute.
Result Volume request
records
not published
No documented cap; constrain result size via latmin/latmax/lonmin/lonmax bounding box, mmsi/imo filters, and the interval (max position age) parameter, and use compress for large payloads.
Feed Quality Condition account
feed quality
10+ vessels, 90%+ uptime (rolling 7 days), <=10s delay
Not a request limit, but API credentials depend on the contributed AIS feed continuously meeting these thresholds.

Policies

Once-Per-Minute Polling
Poll ws.php and stations.php at 60-second or longer intervals; more frequent calls return an empty response.
Filter Before You Fetch
Use bounding box, MMSI/IMO, and interval parameters to request only the vessels you need instead of pulling the global dataset each minute.
Compression for Bulk Pulls
Use compress=1/2/3 (ZIP/GZIP/BZIP2) when pulling large areas to reduce transfer size.

Sources