My flight map is missing from my home page. I even checked several other airports and the same thing. How can this be fixed?
Mine is as well.
Same here, I’m traveling today and it’s been the same since this morning. Just a big blue space. 3 browsers, same result - and I check my Flash with Adobe, it’s current.
Everything looks good at flight aware.com/fix, the only thing that’s gone is the map.
I cannot see the map either on any of the pages (by flight, by airport, or by aircraft type). Sometimes the page shows a blank blue panel where the map should be, sometimes it is just a white panel. It’s been intermittent since 2/2. Chrome 48.0.2564.103 m and Edge both. My flightaware fix page shows no particular issues. I thought it might just be me until I saw this.
Chris
Sorry to hear you’re having issues. I’d like to ask a couple favors to help me troubleshoot the issue:
-
Please paste the URL(s) where you’re having map issues, eg flightaware.com/live/flight/SWA … /KHOU/KLAS. This helps in case this is an issue related to a specific flight (though I see at least one person is having trouble with all maps)
-
Please visit flightaware.com/fix/results and paste the results here (again, I see at least one of you has already looked at this and provided some info).
-
If your browser is issuing any script errors, please paste the contents of those errors here (this would be especially helpful).
So far, I’ve been unable to reproduce the problem, but I do see some sporadic errors in our logs. Unfortunately, they’re not especially helpful as to the nature of the issue…
Thanks!
I haven’t been able to see the maps for several days…not at any of the airports I select, not in the initial page with the flight delays, not in any specific flight tracker. I’ve tried several.
Is it me? I’m on Windows 10 and use Google Chrome. This has been the case just for the last few days; I’ve always been getting the maps prior to this.
Similar lack of maps for me as well. I’ve made no changes to any configuration my end. I was away for a while, but I recall maps working correctly in January. Here’s my info. Hope it helps track down the problem.
Example URLs with issues:
flightaware.com/ (the usual map on the high-right side does not show)
flightaware.com/live/airport/KGEG (any airport I’ve tried gives the same results)
With these URLs there appears only a white box, not even a blue background.
Fix Results:
Your browser is Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
You are not using a mobile device
You are using HTTPS
You may be behind a proxy
- x_forwarded_for: 67.185.82.99
Your public IP address is 67.185.82.99
You are currently logged in.
Your username is XXXX
Your user id is XXXX
Your session id is XXXX
You can accept cookies from FlightAware
You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
You have never chosen a language (locale).
No default locale detected.
Your region is US US/en_US
Your javascript is working fine.
Time (zulu) is Monday, 08-Feb-2016 02:26:48 GMT
JavaScript system clock: Sun Feb 07 2016 18:26:49 GMT-0800 (PST)
JavaScript timezone offset: 480 minutes (8 hours)
Your account can view 4 months of flight history
No errors being produced by browser.
– Mike
Still having the map issue with all maps so here is the information that was requested:
Your browser is Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36
You are not using a mobile device
You are using HTTPS
You may be behind a proxy
- x_forwarded_for: 97.90.117.198
Your public IP address is 97.90.117.198
You are currently logged in.
Your username is ecin
Your user id is 149
Your session id is cc*******…9e**********
You can accept cookies from FlightAware
You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
You have never chosen a language (locale).
No default locale detected.
Your region is US US/en_US
Your javascript is working fine.
Time (zulu) is Monday, 08-Feb-2016 05:22:56 GMT
JavaScript system clock: Sun Feb 07 2016 21:22:58 GMT-0800 (Pacific Standard Time)
JavaScript timezone offset: 480 minutes (8 hours)
Your account can view 4 months of flight history
Browser looks good, no issues that I can see.
Erik
Here’s a few sample pages. I just tried loading KPAE on Edge and it worked, but chrome is still no-go:
Page renders properly, map area is white
flightaware.com/live/airport/KPAE
flightaware.com/live/aircrafttype/B744
Page renders properly, but map is blue blank
flightaware.com/live/flight/BAW4 … /KSEA/EGLL
No browser/script errors
Your browser is Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36
You are not using a mobile device
You are NOT using HTTPS
You do not appear to be behind a proxy server
Your public IP address is 104.200.151.4
You are currently logged in.
Your username is tophalope
Your user id is XXXX
Your session id is 1eXXXXX…3ff29XXXXX
You can accept cookies from FlightAware
You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
You have never chosen a language (locale).
No default locale detected.
Your region is US US/en_US
Your javascript is working fine.
Time (zulu) is Monday, 08-Feb-2016 06:04:28 GMT
JavaScript system clock: Sun Feb 07 2016 22:04:24 GMT-0800 (Pacific Standard Time)
JavaScript timezone offset: 480 minutes (8 hours)
Your account can view 8 months of flight history
For what it’s worth - I’m now getting the maps, but I was getting the exact symptoms you described. The only thing that’s changed is my location, I was in Portland, OR. when I wrote my first message, I’m now in Amsterdam and things are working. Perhaps this information will help FA track this down.
I am now able to reproduce the problem in chrome.
If I use http:// then I get the missing maps. If I use https:// then the maps show up. There doesn’t seems to be particular rhyme or reason as to how one versus the other shows up. If I enter FA via flightaware.com typed into my browser address bar, it defaults to non-HTTPS. If I get a result from a google search that hits a FA link, those are HTTPS. Of course, directly entering a HTTPS works too.
For whatever reason, the same conditions don’t apply in the MSFT Edge browser. I can enter the http:// addresses, and the maps still show.
Chris
Hi all
My maps are all out and have been for 4 days. It seems really odd that everything works except the tracking and real time logging. It’s really odd that the Central Coast of California has the biggest blackout of information. I smell government intervention or jamming maybe to protect the Super Bowl?
In the end I bet that is what it turns out to be. Just an educated guess.
John
Thank you all for the helpful troubleshooting information. So far this appears to be a regional issue, which explains why we can’t reproduce it here in Houston. We’re still trying to nail down the problem, but we’ll keep you updated.
So mine was working this morning for a little while but other than that I haven’t been seeing the maps for a few days now. I’m located on the west coast as well. It’s interesting to me that the diagnostics says I’m using HTTPS even though the URLs I copied are HTTP.
flightaware.com/live/fleet/UAE
flightaware.com/live/flight/JBU1 … /KFLL/TJSJ
flightaware.com/live/airport/KFLL
Your browser is Mozilla/5.0 (iPad; CPU OS 9_2_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13D15 Safari/601.1
You are not using a mobile device
You are using HTTPS
You may be behind a proxy
- x_forwarded_for: 24.21.133.227
Your public IP address is 24.21.133.227
You are currently logged in.
Your username is check6
Your user id is 7660
Your session id is aa4f5a57dd6b…a3cf49160485
You can accept cookies from FlightAware
You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
You have never chosen a language (locale).
No default locale detected.
Your region is US US/en_US
Your javascript is working fine.
Time (zulu) is Monday, 08-Feb-2016 18:32:47 GMT
JavaScript system clock: Mon Feb 08 2016 10:32:47 GMT-0800 (PST)
JavaScript timezone offset: 480 minutes (8 hours)
Your account can view 4 months of flight history
Update: First, thanks again for the information. We discovered that one of our CDN (content distribution network) nodes near Seattle was serving a corrupted version of the JavaScript library that powers our maps. Hence, for most of the world, everything worked fine, but those of you in the PNW area were getting the corrupt file, causing the map failures.
We’ve pushed out an updated version of the JS file with today’s release, and this should address these failures. Please let us know if you continue to have problems.
Thanks for your patience while we worked through the problem.
Makes sense, thanks for the update!
My maps are back up. I’m in CYYC
Thanks
My maps are back online!
Thanks!
Back to normal - thanks!
I’m still having the issue in California.