Feeder lost connections - FA wide problem?

FlightAware ADS-B Flight Tracking
1

Is it known that most of the feeders lost connection to the servers for at least 30 minutes?

First i thought my feeder is the only one, but i’ve checked several feeders in my neighborhood and they all have the same “last checkin” time.
It started some minutes ago where FA sites were unavailable.

Status of my own feeder:

2025-03-26 08:27:49(C) Connection refused. Retrying in 10s
2025-03-26 08:27:58(C) connecting to localhost:30106
2025-03-26 08:27:58(C) Connection refused. Retrying in 10s
2025-03-26 08:27:59(C) connecting to localhost:30106
2025-03-26 08:27:59(C) Connection refused. Retrying in 10s
2025-03-26 08:28:08(C) connecting to localhost:30106
2025-03-26 08:28:08(C) Connection refused. Retrying in 10s
2025-03-26 08:28:09(C) connecting to localhost:30106
2025-03-26 08:28:09(C) Connection refused. Retrying in 10s
2025-03-26 08:28:18(C) connecting to localhost:30106
2025-03-26 08:28:18(C) Connection refused. Retrying in 10s
2025-03-26 08:28:19(C) connecting to localhost:30106
2025-03-26 08:28:19(C) Connection refused. Retrying in 10s
2025-03-26 08:28:28(C) connecting to localhost:30106
2025-03-26 08:28:28(C) Connection refused. Retrying in 10s
2025-03-26 08:28:29(C) connecting to localhost:30106
2025-03-26 08:28:29(C) Connection refused. Retrying in 10s
2025-03-26 08:28:38(C) connecting to localhost:30106
2025-03-26 08:28:38(C) Connection refused. Retrying in 10s
2025-03-26 08:28:39(C) connecting to localhost:30106
2025-03-26 08:28:39(C) Connection refused. Retrying in 10s
2025-03-26 08:28:48(C) connecting to localhost:30106
2025-03-26 08:28:48(C) Connection refused. Retrying in 10s
2025-03-26 08:28:49(C) connecting to localhost:30106
2025-03-26 08:28:49(C) Connection refused. Retrying in 10s
        
piAware Log
systemctl status -n30 piaware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2025-03-26 08:17:09 UTC; 11min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 671 (piaware)
   CGroup: /system.slice/piaware.service
           ├─671 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           └─704 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 10006 --stdout --lat 49.862 --lon 7.813

Mar 26 08:27:11 Airsquitter sudo[738]: pam_unix(sudo:session): session closed for user root
Mar 26 08:27:16 Airsquitter piaware[671]: Lost connection to adept server at 206.253.80.197/1200: server closed connection
Mar 26 08:27:16 Airsquitter piaware[671]: reconnecting in 4 seconds...
Mar 26 08:27:20 Airsquitter piaware[671]: Connecting to FlightAware adept server at 206.253.84.198/1200
Mar 26 08:27:20 Airsquitter piaware[671]: Connection with adept server at 206.253.84.198/1200 established
Mar 26 08:27:21 Airsquitter piaware[671]: TLS handshake with adept server at 206.253.84.198/1200 completed
Mar 26 08:27:21 Airsquitter piaware[671]: FlightAware server certificate validated
Mar 26 08:27:21 Airsquitter piaware[671]: encrypted session established with FlightAware
Mar 26 08:27:21 Airsquitter sudo[753]:  piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Mar 26 08:27:21 Airsquitter sudo[753]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 26 08:27:21 Airsquitter sudo[753]: pam_unix(sudo:session): session closed for user root
Mar 26 08:27:25 Airsquitter piaware[671]: 570 msgs recv'd from rcd (479 in last 1m); 0 msgs sent to FlightAware
Mar 26 08:27:26 Airsquitter piaware[671]: Lost connection to adept server at 206.253.84.198/1200: server closed connection
Mar 26 08:27:26 Airsquitter piaware[671]: reconnecting in 48 seconds...
Mar 26 08:28:14 Airsquitter piaware[671]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Mar 26 08:28:14 Airsquitter piaware[671]: Connection with adept server at piaware.flightaware.com/1200 established
Mar 26 08:28:15 Airsquitter piaware[671]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Mar 26 08:28:15 Airsquitter piaware[671]: reconnecting in 5 seconds...
Mar 26 08:28:20 Airsquitter piaware[671]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Mar 26 08:28:20 Airsquitter piaware[671]: Connection with adept server at piaware.flightaware.com/1200 established
Mar 26 08:28:20 Airsquitter piaware[671]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Mar 26 08:28:20 Airsquitter piaware[671]: reconnecting in 6 seconds...
Mar 26 08:28:26 Airsquitter piaware[671]: Connecting to FlightAware adept server at 206.253.80.198/1200
Mar 26 08:28:26 Airsquitter piaware[671]: Connection with adept server at 206.253.80.198/1200 established
Mar 26 08:28:26 Airsquitter piaware[671]: TLS handshake with adept server at 206.253.80.198/1200 failed: handshake failed: software caused connection abort
Mar 26 08:28:26 Airsquitter piaware[671]: reconnecting in 4 seconds...
Mar 26 08:28:30 Airsquitter piaware[671]: Connecting to FlightAware adept server at 206.253.84.195/1200
Mar 26 08:28:30 Airsquitter piaware[671]: Connection with adept server at 206.253.84.195/1200 established
Mar 26 08:28:30 Airsquitter piaware[671]: TLS handshake with adept server at 206.253.84.195/1200 failed: handshake failed: software caused connection abort
Mar 26 08:28:30 Airsquitter piaware[671]: reconnecting in 58 seconds...
1 Like
2

Looks like mine have been down for over an hour too

1 Like
3

Seem to be that almost all feeders are impacted. I’ve checked some others, having the same trouble.

1 Like
4

yep same here since 08 UTC, local reception is still fine, seems that it’s a serverside problem. Skyaware anywehere is also running normally.

2 Likes
5

Same here. Feeds to other sites are working properly, so the FA staff might need to look into it. Depending on their location it can be a night shift :laughing:

EDIT:

Seem to be a global problem. Client tried several different (virtual) servers, but all failed so far:

image
image773×288 8.58 KB

None of these seem to be reachable currently:

206.253.80.196 206.253.80.197 206.253.80.198 206.253.80.199 
206.253.80.200 206.253.80.201 206.253.84.193 206.253.84.194 
206.253.84.195 206.253.84.196 206.253.84.197 206.253.84.198
1 Like
6

Same issue for me .. restarted my Pi incase it was that but other sites being fed are receiving ok

7

Seem to be working again since a short time.

Feeder checked in successfully, Stats are updated. Reboot wasn’t required
Connection established at 10:01 CET, maybe that’s the reason why you’ve seen others already working again.

1 Like
8

This was an internal problem that affected new (re)connection attempts (established connections were unaffected) and delayed stats updates for ~2 hours; everything should be back to normal now.

3 Likes
9

Hm, i cannot confirm that statement. I haven’t changed my feed for weeks, the device had an uptime of > 1 week during the given time.

However… if it works again, all good :slight_smile: