Hello ADSBexchange Team,
I am reporting a significant data ingestion issue for my station in Puerto Rico (NW4A-PR / norpr). While the station tracks 11M+ positions/month on other platforms, ADSBexchange is only receiving a fraction of this data due to severe packet loss on the internet backbone.
Evidence of Routing Issue: I performed an MTR from my station to feed1.adsbexchange.com (currently resolving to us-west-2). While my local ISP and the Caribbean undersea hops are clean (0% loss), I am seeing ~8.3% packet loss at the GTT backbone node in Denver (ae9.cr5-den2.ip4.gtt.net).
Impact: This loss is triggering the “High latency, reducing data usage temporarily” state in the adsbexchange-feed service, causing a massive drop in reported positions and ranking despite a healthy 98ms baseline latency and 390NM+ local reach.
Regional Observations: Additionally, the Region 6 (Caribbean) MLAT sync table on the website is frequently appearing empty, though my local logs show successful synchronization with 11 peers.
I have attached the full MTR output below for your network team. Is there any possibility of adjusting the ingestion routing for the Caribbean region to avoid this lossy path through Denver? My traceroute [v0.95]
pi24-bookworm (10.1.5.90) → feed1.adsbexchange.com (34.218.252026-03-03T23:07:15+0000
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. XXXXXX 0.0% 12 4.2 4.5 4.2 6.2 0.7
2. XXXXXX 0.0% 12 4.3 4.5 4.2 6.7 0.7
3. 10.162.6.145 0.0% 12 4.6 4.8 4.5 5.6 0.3
4. 10.255.110.245 0.0% 12 4.9 5.1 4.8 6.2 0.4
5. 192.254.98.114 0.0% 12 5.3 9.3 5.0 30.6 8.1
6. 74.119.26.64 0.0% 12 26.1 26.5 26.1 27.8 0.5
7. 76.74.57.181 0.0% 12 26.8 35.3 26.3 71.4 15.1
8. ae9.cr5-den2.ip4.gtt.net 8.3% 12 77.9 78.0 77.8 79.2 0.4
9. (waiting for reply)
10. 108.166.232.36 0.0% 12 98.1 98.4 98.0 100.1 0.6
11. (waiting for reply)
12. (waiting for reply)
13. (waiting for reply)
14. ec2-34-218-254-209.us-west-2.compute.am 0.0% 11 97.8 97.9 97.7 98.8 0.3