I run the latest version of Firefox under Windows XP. For the last few weeks, FlightAware has timed out during routine updates. This happens several times a day, with no perceived pattern.
Is anyone else seeing this problem?
Timeout sounds like a connectivity issue between you and us rather than something browser specific. Are there any other computers at the same location and does the same issue occur?
Can you post the output of flightaware.com/fix (minus your session id) and the output of “tracert flightaware.com” and “tracert e0.flightcdn.com” in a command prompt?
Session Diagnostics
* Your browser is Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15 (.NET CLR 3.5.30729)
* You are not using a mobile device
* You may be behind a proxy
- x_forwarded_for: 74.123.19.115
* Your public IP address is 74.123.19.115
* You are currently logged in.
* Your username is OldNick
* Your user id is 319904
* Your session id is
* 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).
* Your default language is English (USA) (en_US)
* Your region is US US/en_US
* Your javascript is working fine.
* Time (zulu) is Monday, 14-Mar-2011 18:40:20 GMT
* Your account can view 4 months of flight history
I cannot get the tracert commands to work for me.
1 77 ms 1 ms <1 ms 74.123.16.1
2 28 ms 27 ms 29 ms core-01-g4-22-113.lsvokyqy.cinergycom.net [72.4.
2.153]
3 29 ms 30 ms 32 ms agg-01-g4-23.iplwin75.cinergycom.net [72.4.78.41
]
4 19 ms 19 ms 18 ms ge-2-3-0-500.chc-core-r2.norlight.net [66.84.254
.1]
5 37 ms 36 ms 30 ms ge-6-24.car3.Chicago1.Level3.net [4.71.100.1]
6 38 ms 28 ms 37 ms ae-11-51.car1.Chicago1.Level3.net [4.69.138.3]
7 38 ms 38 ms 40 ms dcr1-ge-2-0-0.chicago.savvis.net [208.175.10.1]
8 30 ms 34 ms 36 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.113]
9 77 ms 59 ms 53 ms cr1-pos-0-3-3-1.SanFrancisco.savvis.net [204.70.
194.74]
10 60 ms 62 ms 77 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.1
96.30]
11 209 ms 224 ms 218 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.
145]
12 38 ms 46 ms 44 ms 208.175.175.54
13 54 ms * 49 ms border1.ge4-1-bbnet2.ext1a.dal.pnap.net [216.52.
191.84]
14 69 ms 57 ms 67 ms core5.te4-3.hou-dal-ext1-1171.hou.pnap.net [63.2
51.44.42]
15 65 ms 67 ms 65 ms border10.ge6-2-bbnet2.hou.pnap.net [216.52.168.8
3]
16 * * * Request timed out.
The second tracert run closes itself before I can do a copy. Maybe this one will help.
Tracing route to ne1.wac.edgecastcdn.net [72.21.91.19]
over a maximum of 30 hops:
1 1 ms 2 ms <1 ms 74.123.16.1
2 29 ms 28 ms 25 ms core-01-g4-22-113.lsvokyqy.cinergycom.net [72.4.
2.153]
3 33 ms * 34 ms agg-01-g4-23.iplwin75.cinergycom.net [72.4.78.41
]
4 164 ms 37 ms 39 ms ge-2-3-0-500.chc-core-r2.norlight.net [66.84.254
.1]
5 * * * Request timed out.
6 89 ms 39 ms
This is the second tracert command that you requested.
This is what I got when it timed out:
Tracing route to flightaware.com [70.42.6.250]
over a maximum of 30 hops:
1 <1 ms <1 ms 2 ms 74.123.16.1
2 28 ms 23 ms 22 ms core-01-g4-22-113.lsvokyqy.cinergycom.net [72.4.
2.153]
3 27 ms 26 ms 28 ms agg-01-g4-23.iplwin75.cinergycom.net [72.4.78.41
]
4 41 ms 29 ms 32 ms ge-2-3-0-500.chc-core-r2.norlight.net [66.84.254
.1]
5 36 ms * 37 ms ge-6-24.car3.Chicago1.Level3.net [4.71.100.1]
6 40 ms * 39 ms ae-11-51.car1.Chicago1.Level3.net [4.69.138.3]
7 * 40 ms * dcr1-ge-2-0-0.chicago.savvis.net [208.175.10.1]
8 40 ms 39 ms * cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.113]
9 66 ms 67 ms 69 ms cr1-pos-0-3-3-1.SanFrancisco.savvis.net [204.70.
194.74]
10 67 ms 76 ms 63 ms dpr1-ge-4-0-0.dallasequinix.savvis.net [204.70.1
96.30]
11 64 ms 67 ms 69 ms er1-te-2-1.dallasequinix.savvis.net [204.70.204.
145]
12 52 ms 51 ms 59 ms 208.175.175.54
13 61 ms * 59 ms border1.ge4-1-bbnet2.ext1a.dal.pnap.net [216.52.
191.84]
14 69 ms 69 ms 65 ms core5.te4-3.hou-dal-ext1-1171.hou.pnap.net [63.2
51.44.42]
15 62 ms 65 ms 67 ms border10.ge6-2-bbnet2.hou.pnap.net [216.52.168.8
3]
16 * * * Request timed out.
17
Thanks for posting, unfortunately I don’t see anything that points to a cause.
At the moment the timeout occurs, can you load other websites fine?
Yes. Everything else works fine with this browser.
When I find it timed out, I just hit the bookmark for FlightAware, re-enter KTHA for the local airport, and it comes right back.
Thanks for the effort you have made on my behalf. I just figured that something changed, because your site has worked fine for several years, until just recently.
Is there a way to define a default airport (KTHA) so that I do not have to retype it each time I restart the site?
Bookmark it: flightaware.com/live/airport/KTHA
Thanks. That sounds simple enough!