About half an hour ago I noticed Total Aircraft on Skyaware dropped to zero. It stayed at zero for a few minutes before starting to go back up but stopped at 12 aircraft and then after a few minutes went back up to 120. It has done this about half a dozen times in the last 25-30 minutes.
I powercycled the feeder hardware but its is still doing it.
The last few entries in the UltraFeeder log:
- [2026-09-26 16:51:32.987][adsbx-stats] curl: (28) Operation timed out after 10001 milliseconds with 0 bytes received
- [2026-09-26 16:51:33.012][adsbx-stats] WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
- [2026-09-26 16:51:37.266][mlat-client][feed.adsbexchange.com] peer_count: 80 outlier_percent: 0.8 bad_sync_timeout: 94
- [2026-09-26 16:51:52.381][mlat-client][feed.adsbexchange.com] peer_count: 78 outlier_percent: 0.8 bad_sync_timeout: 79
- [2026-09-26 16:52:07.553][mlat-client][feed.adsbexchange.com] peer_count: 80 outlier_percent: 0.7 bad_sync_timeout: 64
- [2026-09-26 16:52:22.715][mlat-client][feed.adsbexchange.com] peer_count: 80 outlier_percent: 0.7 bad_sync_timeout: 49
- [2026-09-26 16:52:37.818][mlat-client][feed.adsbexchange.com] peer_count: 81 outlier_percent: 0.6 bad_sync_timeout: 34
- [2026-09-26 16:52:52.478][mlat-client][feed.adsbexchange.com] peer_count: 80 outlier_percent: 0.6 bad_sync_timeout: 19
- [2026-09-26 16:53:08.104][mlat-client][feed.adsbexchange.com] peer_count: 79 outlier_percent: 0.6 bad_sync_timeout: 4
- [2026-09-26 16:53:19.767][readsb] BeastReduce TCP output: feed1.adsbexchange.com port 30004: Bad connection, dropping data (connection lost 0.0% of data) (suppress msg for 300 s)
I just checked my 2 ADSB.im systems but they had no issues today.
Could it be your RPi3 acting up again? I have an adsbexchange feeder running alongside my Piaware, and apparently, it hasn’t disconnected or stopped sending data. MLAT doesn’t work in my area because there aren’t enough peers…
Thanks for the replies guys. I tracked it down to issues with my internet. I will be SO glad when we can finally get a decent stable internet connection in the area!
I’ve experienced disconnection issues before, and the culprit wasn’t the internet connection itself—it was the power supply. I have a remote setup that runs on off-grid solar power. When I was using an XL4015 module (to step down the 24V battery voltage to the 5V required by the Raspberry Pi), I would occasionally experience disconnections, always in the morning. The diagnosis was that rapid fluctuations in battery voltage were causing instability in the XL4015’s 5V DC output; this caused the RPi to either lose its LAN interface IP address or suffer UDP packet loss (ranging from 15% to 60%). Water pumps run on this solar system during the morning, and whenever clouds covered the sun, the battery voltage would plummet. When the sun came back out, the voltage would shoot up just as quickly. The solution was to connect a laptop power brick (19V/3A) to an off-grid inverter (converting 24V to 220V) to supply power to the XL4015 mounted on the mast. Once I did this, the voltage stabilized, and the IP address loss issues stopped.
When these problems happen again—if they do—you need a PC to test the routes used by your RPi. You should test for UDP packet loss, run traceroutes, pings, etc., to the target servers of the aggregators you use, and verify whether the issue actually lies with the connection.
1 Like
I had occasional issues in t he last 2 months resulting in some sites losing the connection with one of the aggregators. In my case it was always FR24 that would complain first and usually after a day or 2/3 after a modem reboot.
I was using the ISP provided equipment but that had a tough time keeping up with the extensive network at my place. If everything is switched on I have 125 active IP addresses in the network at that point in time. But after waking up twice last week with a network outage due to the ISP modem I had enough. The ISP equipment could be upgraded by the ISP at their convenience resulting in outages, firmware upgrades causing communication issues between modem and accesspoints, a partial gui (all Wi-Fi equipment visible, all LAN connections not displaying) and sometimes being unable to do the most simple things. For example to revert a IP reservation you could only get to that by factory resetting the modem. Needless to say that they didn’t supply a back-up function so you had to rebuild it from scratch again. And to top it all of you had to reset the access points prior to the 7days marker, once you passed that then a reboot of the entire modem and access points was mandatory to get communication back.
I switched to privately owned equipment from a reputable European brand (Fritzbox) and replaced the modem and the access points with a dedicated router and 6 access points. I had 7 accesspoints connected to the ISP equipment. That has been up now for 4 days with out a hitch, everything stayed online and I haven’t had a single second of downtime on all of the 24 feeders.
Surely it wasn’t cheap, just over 900 euro’s but a peace of mind without resetting the access points weekly is also worth something.
I should be future proof for a while, Wi-Fi 7 on all networking equipment, router has a 10 GB WAN, 1x 10GB LAN and 3x 2,5GB LAN interfaces.The network has 1 GB interfaces but if I want to upgrade that hardware it is an option now ( I’d first have to rob a bank when looking at current hardware prices 
)
1 Like
Do you sell internet to neighbors or other people? Wow! That’s an insane setup. I have a MikroTik RB750Gr3 and I already have more than enough capacity, haha.
Nope, not selling at all, I have a fully connected Smarthome built on open source and run a private network where everything is connected wired with some exceptions. Every room has a dedicated switch and sometimes more than 1 switch when needed. All switches are Cisco managed switches.
I have a 1 GB fiber connection at my home and I could upgrade to 4 GB if I would want to.
I’d like to be prepared for future upgrades so the network should be up to it in its capabilities.
1 Like
