Since a few weeks I’m getting notifications that some of the setups have not reported in at Flightaware.
When checking the logs they are normally reporting but it can take up to 20-30 minutes before the notification is cleared again.
Last time this happened was in 2021 when something on the backend of the FA servers was changed. Has there been a change again causing this behavior?
The stations are reporting normally and the statistics are also fine just wondering why this message keeps popping up at irregular times on different setups.
On my stats page right now it says last feeder update half hour ago, even though right above it says last update a minute ago. Also all the indicators are red: PiAware,FlightAware, MLAT, even though on piaware-web they are green. None of this seems to matter however since stat totals are updating on stats page. This is on station 180204.
This isn’t a browser issue but a server backend issue. One of my stations is reporting it had the last contact 1 hour ago where it did report in just minutes ago. It is a cosmetic thing since the reporting is running as expected. 2 stations display this behavior, the other 19 don’t. If it was a browser thing they would all have the same issue
My site check in intervals have returned to my normal 2 to 3 minute check ins. Return to normal has been constant for over 24 hours now without any actions taken on my part.
I am still getting this problem on and off. In fact, seeing the problem this morning is what led me to this thread. After reading this thread, I went to do a screen print and everything was updated. If and when I catch the all red and l-o-n-g time since check-in next time on the Site Information tab, I’ll grab a screen print then.
Yep … I checked about six or seven minutes ago and the Site Information section said my feeder had not checked in - in 36 minutes, yet the Nearby Site section said my last check-in was 6 minutes ago. I’m glad I grabbed the screen printed as soon as I saw all the red because when I went back, the Site Information had updated correctly.
Yes, that makes sense. I’m a bit surprised we haven’t seen any recent response from FA providing some feedback/status. My instance of the problem has been resolved somehow for some time now with no understanding of why that is. Makes me think it’s based on the individual server involved in my feeder monitoring vs yours and others experiencing the issue.
for the information from my setups. If other numbers show the same I will follow that up with the additional numbers
