Am I the only one seeing this?
https://www.isitdownrightnow.com/flightaware.com.html
It’s back online now.
1 Like
I can’t get the stats pages for any of the three accounts I look after and they’re all reporting FlightAware down and MLAT status red when I look at their PiAware Status pages.
mlat-status on them all reports that they’re synchronised with nearby receivers and I am showing connected to ADSBx successfully with MLAT so it looks like it’s something here.
I’m seeing both Flightaware and Flightradar24 as being down. My logs show FR24 down first followed by Flightaware about 10 minutes later, starting almost two hours ago. Multiple airline sites down too.
Thought that it was just a network issue, and checked isitdownrightnow.com and it showed both down.
Puzzling…
1 Like
It’s been down for at least a couple of hours now for me…
Yes, has been down for me for 2 hours but has just come back working on 20:40pm in UK… Mine showed 6-8 pm.
I noticed in the display you get of nearby people that several were shown as down for 2 hours but several others like me were on just 2-5 mins - so they had restarted like me . Strangely my Flightaware now shows down only 7-8pm.
Geoff
Again stopped working at 20:44pm in UK. Still down at 20:58.
Geoff
Data still seems to be being sent to Flightaware, and MLAT is still working here. Piaware log extract:
Sep 28 06:07:00 raspi4 piaware[690]: mlat-client(13131): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
Sep 28 06:07:00 raspi4 piaware[690]: mlat-client(13131): Results: 0.3 positions/minute
Sep 28 06:07:00 raspi4 piaware[690]: mlat-client(13131): Aircraft: 1 of 1 Mode S, 2 of 2 ADS-B used
Sep 28 06:11:13 raspi4 piaware[690]: 221137 msgs recv'd from dump1090-fa (117 in last 5m); 220807 msgs sent to FlightAware
Sep 28 06:16:13 raspi4 piaware[690]: 221173 msgs recv'd from dump1090-fa (36 in last 5m); 220843 msgs sent to FlightAware
Sep 28 06:21:13 raspi4 piaware[690]: 221207 msgs recv'd from dump1090-fa (34 in last 5m); 220877 msgs sent to FlightAware
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Receiver status: connected
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Server status: not synchronized with any nearby receivers
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Receiver: 6.0 msg/s received 3.4 msg/s processed (57%)
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Results: 2.2 positions/minute
Sep 28 06:22:00 raspi4 piaware[690]: mlat-client(13131): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Sep 28 06:25:52 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:25:52 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:25:52 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:26:13 raspi4 piaware[690]: 221208 msgs recv'd from dump1090-fa (1 in last 5m); 220878 msgs sent to FlightAware
Sep 28 06:29:39 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:29:39 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:29:39 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:31:13 raspi4 piaware[690]: 221208 msgs recv'd from dump1090-fa (0 in last 5m); 220878 msgs sent to FlightAware
Sep 28 06:34:50 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:34:50 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:34:50 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:36:13 raspi4 piaware[690]: 221208 msgs recv'd from dump1090-fa (0 in last 5m); 220878 msgs sent to FlightAware
Sep 28 06:37:00 raspi4 piaware[690]: mlat-client(13131): Receiver status: connected
Sep 28 06:37:00 raspi4 piaware[690]: mlat-client(13131): Server status: not synchronized with any nearby receivers
Sep 28 06:37:00 raspi4 piaware[690]: mlat-client(13131): Receiver: 0.0 msg/s received 0.0 msg/s processed (38%)
Sep 28 06:37:00 raspi4 piaware[690]: mlat-client(13131): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Sep 28 06:37:00 raspi4 piaware[690]: mlat-client(13131): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Sep 28 06:37:20 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:37:20 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:37:20 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:39:51 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:39:51 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:39:51 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:41:13 raspi4 piaware[690]: 221208 msgs recv'd from dump1090-fa (0 in last 5m); 220878 msgs sent to FlightAware
Sep 28 06:42:21 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:42:21 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:42:21 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:44:51 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Sep 28 06:44:51 raspi4 piaware[690]: mlat-client(13131): Input connected to localhost:30005
Sep 28 06:44:51 raspi4 piaware[690]: mlat-client(13131): Input format changed to BEAST, 12MHz clock
Sep 28 06:46:13 raspi4 piaware[690]: 221220 msgs recv'd from dump1090-fa (12 in last 5m); 220890 msgs sent to FlightAware
Sep 28 06:51:13 raspi4 piaware[690]: 221263 msgs recv'd from dump1090-fa (43 in last 5m); 220933 msgs sent to FlightAware
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Receiver status: connected
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Server status: synchronized with 13 nearby receivers
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Receiver: 2.5 msg/s received 1.8 msg/s processed (73%)
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Results: 0.7 positions/minute
Sep 28 06:52:01 raspi4 piaware[690]: mlat-client(13131): Aircraft: 1 of 1 Mode S, 2 of 2 ADS-B used
Sep 28 06:56:13 raspi4 piaware[690]: 221361 msgs recv'd from dump1090-fa (98 in last 5m); 221031 msgs sent to FlightAware
Sep 28 07:01:13 raspi4 piaware[690]: 221483 msgs recv'd from dump1090-fa (122 in last 5m); 221153 msgs sent to FlightAware
Sep 28 07:06:13 raspi4 piaware[690]: 221603 msgs recv'd from dump1090-fa (120 in last 5m); 221273 msgs sent to FlightAware
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Receiver status: connected
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Server status: synchronized with 82 nearby receivers
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Receiver: 15.7 msg/s received 10.4 msg/s processed (66%)
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Results: 6.3 positions/minute
Sep 28 07:07:01 raspi4 piaware[690]: mlat-client(13131): Aircraft: 0 of 1 Mode S, 4 of 4 ADS-B used
Sep 28 07:08:11 raspi4 piaware[690]: timed out waiting for alive message from FlightAware, reconnecting...
Sep 28 07:08:11 raspi4 piaware[690]: multilateration data no longer required, disabling mlat client
Sep 28 07:08:12 raspi4 piaware[690]: fa-mlat-client exited normally
Sep 28 07:08:12 raspi4 piaware[690]: reconnecting in 5 seconds...
Sep 28 07:08:12 raspi4 piaware[690]: mlat-client(13131): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Sep 28 07:08:12 raspi4 piaware[690]: mlat-client(13131): Exiting on connection loss
Sep 28 07:08:17 raspi4 piaware[690]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 28 07:08:32 raspi4 piaware[690]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Sep 28 07:08:32 raspi4 piaware[690]: reconnecting in 4 seconds...
Sep 28 07:08:36 raspi4 piaware[690]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 28 07:08:51 raspi4 piaware[690]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Sep 28 07:08:51 raspi4 piaware[690]: reconnecting in 5 seconds...
Sep 28 07:08:56 raspi4 piaware[690]: Connecting to FlightAware adept server at 70.42.6.156/1200
Sep 28 07:09:11 raspi4 piaware[690]: Connection attempt with adept server at 70.42.6.156/1200 timed out
Sep 28 07:09:11 raspi4 piaware[690]: reconnecting in 5 seconds...
There are very few aircraft around at the moment, so MLAT not in use unless a non-ADSB aircraft is visible.
Times are UTC +10
Looks like feeding and MLAT came back about an hour and twenty minutes ago, and the website appears to be back to normal again.
Curious about the origin, but more importantly glad they are back.
Yeah me too here in Florida USA. I’m missing 2 hours of data. Many refreshes and all just timed out. I finally checked it now and it appears to be back up normally.
Unexpected Maintenance 
heh heh.
Looks like it was a global issue.
Located in Germany i realized the same outage yesterday evening for a certain amount of time between 0700pm and 0900pm local time.
That seem to be a network carrier issue. Or did we miss a general statement bringing everything down for a specific reason?
FR24 seem to be still down. I am getting a Cloudflare Error 502
On Twitter they made a statement for the downtime yesterday:
Has been up and down all day, as has FR24. Both my RPi and FR24 box lost connection to the servers and required a reboot to fix it, once both sites were back of course.
What is most frustrating is that FlightAware doesn’t seem to want to acknowledge the ongoing problems. There has been no information posted anywhere, including on their twitter account. If anyone FA Staff is reading this: please tell us what is going on! I’m sure you are all quite aware that you are impacting many people and businesses right now that rely (and pay) for your services and data. The least you can do is let us know what’s going on, what you’re doing to fix it, and when we can expect to return to normal.
Thank you
Outage announcements are published on Twitter @flightawareops. There have been numerous posts there over the last few hours as our operations team continues to address the networking issue.
Ah, I didn’t realize there was a separate twitter account for it. Thanks! Now let’s just hope the issues can be resolved soon.
not sure if the feeders are impacted, at least it is not documented.
But both of my feeders and some others in the direct neighborhood showing a clear downtrend the last few hours.
The devices themselves do not show this strong downtrend locally
In Piaware log i have several entries of these, followed by reconnect attempt messages
data isn't making it to FlightAware, reconnecting...
FR24 still seems a bit flakey. I had an email overnight telling me I stopped feeding them last night, I logged in there just now and it said I’m offline so I rebooted my Pi and now their site is telling me my username and password are incorrect.
I received this email from FR24 a couple of hours ago.
Hi,
For the third time in two days Flightradar24 is under attack. Our engineers are working to mitigate the attack as quickly as possible and we hope to be back tracking flights soon. We appreciate your patience and apologize for the inconvenience.
With best regards,
team Flightradar24
That explain a lot.
I can remember a cyber attack at Garmin a few weeks ago. They were required to shutdown the whole network including manufacturing and customer services for several days.
In the US today a Fortune 500 hospital chain (90,000 employees at 250 facilities) was hit with a massive cyberattack. They are using paper records. Even the wifi instruments/monitors are down.
The Emergency 911 system is suffering outages from Washington state to Washington DC. Minneapolis was hard hit, too. It makes one wonder if these attacks are coordinated.
A few days ago someone died due to shutdown based on a cyberattack in a hospital in Germany.
The hackers made a mistake and handed over the decrypt code for free. But it was too late.
They targeted a university but hit the hospital
In such an event the whole network must be shut down with all devices as long as they are not isolated properly.
Garmin shut down their phone system as well as it’s connected to the network.