Skip to main content

Troubleshooting

Platform not reachable​

Check the endpoint URL (stream.adsbexchange.com:443), your firewall, and any VPN that might be blocking outbound traffic to port 443.

Invalid ClientId or SubscriptionId​

Both must be valid GUIDs. Confirm the values you're sending match the ones JETNET issued.

Subscription not found​

The subscription must exist and belong to the client whose ID you're presenting in the client-id metadata header. If you've recently rotated credentials, make sure you're using the matching pair.

No data​

Remove any active filters temporarily to confirm the underlying stream is delivering. If you still see no data, contact JETNET to confirm your stream and region access are active.

Records with missing fields, no position, or a string altitude​

This is expected, not a bug. Records are sparse: only event_type, hex, and type are always present, and any other field is omitted (never sent as null) when unavailable. Two cases commonly surprise new consumers:

  • A record has no lat/lon — the aircraft is tracked but has no current valid position. You may use lastPosition or rr_lat/rr_lon, or drop the record.
  • alt_baro is sometimes the string "ground" instead of a number — a deliberate on-surface indicator, not a malformed value.

See the Aircraft reference for the full field rules and handling notes.