FlightAware Discussions

Houston, we have a problem - flightaware.com outage

Noticed some intermittent errors in piaware, also flightaware.com is down.

chrome_QB2jxcRzDm

Jun 16 11:08:34 picm4 piaware[579]: mlat-client(3702): Exiting on connection loss
Jun 16 11:08:39 picm4 piaware[579]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 16 11:08:39 picm4 piaware[579]: Connection with adept server at piaware.flightaware.com/1200 established
Jun 16 11:08:39 picm4 piaware[579]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: software caused connection abort
Jun 16 11:08:39 picm4 piaware[579]: reconnecting in 6 seconds...
Jun 16 11:08:45 picm4 piaware[579]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 16 11:08:53 picm4 piaware[579]: Connection with adept server at piaware.flightaware.com/1200 established
Jun 16 11:09:00 picm4 piaware[579]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Jun 16 11:09:00 picm4 piaware[579]: reconnecting in 5 seconds...
Jun 16 11:09:05 picm4 piaware[579]: Connecting to FlightAware adept server at 70.42.6.232/1200
Jun 16 11:09:20 picm4 piaware[579]: Connection attempt with adept server at 70.42.6.232/1200 timed out
Jun 16 11:09:20 picm4 piaware[579]: reconnecting in 4 seconds...
Jun 16 11:09:24 picm4 piaware[579]: Connecting to FlightAware adept server at 70.42.6.228/1200
Jun 16 11:09:39 picm4 piaware[579]: Connection attempt with adept server at 70.42.6.228/1200 timed out
Jun 16 11:09:39 picm4 piaware[579]: reconnecting in 4 seconds...
Jun 16 11:09:43 picm4 piaware[579]: Connecting to FlightAware adept server at 70.42.6.224/1200
Jun 16 11:09:44 picm4 piaware[579]: Connection with adept server at 70.42.6.224/1200 established
Jun 16 11:09:44 picm4 piaware[579]: TLS handshake with adept server at 70.42.6.224/1200 failed: handshake failed: software caused connection abort
Jun 16 11:09:44 picm4 piaware[579]: reconnecting in 5 seconds...

Same here in Germany. Seem to be a global issue

Jun 16 20:40:39 Raspy piaware[606]: TLS handshake with adept server at 70.42.6.225/1200 failed: handshake failed: software caused co
Jun 16 20:40:39 Raspy piaware[606]: reconnecting in 5 seconds...
Jun 16 20:40:44 Raspy piaware[606]: Connecting to FlightAware adept server at 70.42.6.198/1200
Jun 16 20:40:44 Raspy piaware[606]: Connection with adept server at 70.42.6.198/1200 established
Jun 16 20:40:44 Raspy piaware[606]: TLS handshake with adept server at 70.42.6.198/1200 failed: handshake failed: software caused co
Jun 16 20:40:44 Raspy piaware[606]: reconnecting in 5 seconds...
Jun 16 20:40:49 Raspy piaware[606]: Connecting to FlightAware adept server at 70.42.6.224/1200
Jun 16 20:40:50 Raspy piaware[606]: Connection with adept server at 70.42.6.224/1200 established
Jun 16 20:40:50 Raspy piaware[606]: TLS handshake with adept server at 70.42.6.224/1200 failed: handshake failed: software caused co
Jun 16 20:40:50 Raspy piaware[606]: reconnecting in 4 seconds...

Interestingly only one of my two feeders is down:

image

image

Last checkin was at around 40 Minutes ago

It’s back up…1445 hrs EDT

Confirmed. My “down” receiver is connected again, however the stats are not yet updated. There it still shows down.

Jun 16 20:42:11 Raspy piaware[606]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localho
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): fa-mlat-client 0.2.11 starting up
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Using UDP transport to 2600:c13:1002:4::228 port 15773
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Listening for Beast-format results connection on port 30105
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Listening for Extended Basestation-format results connection on port 30106
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Route MTU changed to 1492
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Input connected to localhost:30005
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Input format changed to BEAST, 12MHz clock
Jun 16 20:42:12 Raspy piaware[606]: mlat-client(14987): Beast-format results connection with ::1:30104: connection established
Jun 16 20:42:40 Raspy piaware[606]: 613051 msgs recv'd from readsb (399 in last 5m); 607987 msgs sent to FlightAware

Ya, came back up right after I posted. Looks like most of the stats survived despite nearly an hour of issues.

1 Like

Seem to be that not all receivers were affected. Checked the ones around me, some showed the outage, others were running as usual

Down again… Connection is flapping

No more errors here yet. I did notice a chunk of stats lost, but better than my nearby stations!

I was only poking around since it looks like we’re having some minor tropo fun on the map around here today.