# Unable to access FlightAware

**URL:** <https://discussions.flightaware.com/t/unable-to-access-flightaware/85368>\
**Category:** General\
**Created:** [November 15, 2022, 10:37am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368 "2022-11-15T10:37:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 15, 2022, 10:37am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/1 "2022-11-15T10:37:13Z")

</div>

For the last few days, maybe 5 or so, I have had trouble connecting to the [FlightAware.com](http://FlightAware.com) website. This happens almost every time I try connect. I say “almost” because once or twice I have successfully connected.  
When going to the URL, after waiting for around 30 seconds while the browser tries to connect, Chrome pops up a message (with a sad face emoji picture) : This site can’t be reached. The connection was reset. Try : Checking the connection. Checking the proxy and firewall. Running Windows Network Diagnostics. Followed by - ERR\_CONNECTION\_RESET with a “reload” button below.  
On the few occasions that I did connect, if I was reading squawks and tried to go back to my stats page, it would have the same problem of not connecting.  
I have the URL for my stats page saved as a bookmark, which always used to work. Now it doesn’t. I have lately been trying just the [flightaware.com](http://flightaware.com) URL, but that also doesn’t work.  
I have cleared my browser cache, but to no avail.  
Any ideas? Or is flightaware simply down?

---

<div class="post-metadata">

**Author:** ![foxhunter](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxhunter/32/113733_2.png) [@foxhunter](https://discussions.flightaware.com/u/foxhunter)\
**Post date:** [November 15, 2022, 12:58pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/2 "2022-11-15T12:58:11Z")

</div>

On the time you get the problem you can simply check using a different site like  
[Is it down? Check at Down for Everyone or Just Me](https://downforeveryoneorjustme.com/)

Then you can see if the site is really unavailable or if it’s only you.

Like this:  
 ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/4/6/4669c0707ec9e3d5d9258872887f89b2f9f1b918.png)

---

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 15, 2022, 1:28pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/3 "2022-11-15T13:28:09Z")

</div>

Thanks. It says it is just me. But I am only having this issue with flightaware, everything else is perfect. It just stopped suddenly one day, and nothing my side has changed. I have no idea what else to try.

---

<div class="post-metadata">

**Author:** ![foxhunter](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxhunter/32/113733_2.png) [@foxhunter](https://discussions.flightaware.com/u/foxhunter)\
**Post date:** [November 15, 2022, 1:40pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/4 "2022-11-15T13:40:50Z")

</div>

There are a couple of things to be checked but it’s harder while not having the device in front of me.

Try a different device (if available) or a different browser on that device where it is not working just to eliminate any side effects

---

<div class="post-metadata">

**Author:** ![jparker3](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jparker3/32/107153_2.png) [@jparker3](https://discussions.flightaware.com/u/jparker3)\
**Post date:** [November 15, 2022, 7:31pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/5 "2022-11-15T19:31:33Z")

</div>

I’m having the same issues. [Flightaware.com](http://Flightaware.com) is the only thing that will not work and that is useing chrome and edge

---

<div class="post-metadata">

**Author:** ![michaelgiebisch](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/michaelgiebisch/32/109122_2.png) [@michaelgiebisch](https://discussions.flightaware.com/u/michaelgiebisch)\
**Post date:** [November 16, 2022, 5:07am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/6 "2022-11-16T05:07:19Z")

</div>

I have exactly the same problem; chat request get answered that FA support is currently looking for troubleshooting. In my history problem appeared after Windows 10 updates Nov 12 - maybe Windows 11 will run better? Anyone else who can share experience about that?

---

<div class="post-metadata">

**Author:** ![dvsvejk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dvsvejk/32/136416_2.png) [@dvsvejk](https://discussions.flightaware.com/u/dvsvejk)\
**Post date:** [November 16, 2022, 6:34am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/7 "2022-11-16T06:34:42Z")

</div>

I rarely use Windows/Edge on my dual-boot laptop, but tried it out as a test. When trying to connect to my Pi I also got an error page for about 30 seconds then it connected and worked fine afterwards to include the stats page and flightaware main site. Poking around the Edge settings I saw a new update was available so I forced that. Still works OK after that. It seems patch Tuesday had some unintended consequences for some.

FWIW my system is Windows 11 22H2, Edge version 107.0.1418.42

---

<div class="post-metadata">

**Author:** ![tgpopel](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/tgpopel/32/118533_2.png) [@tgpopel](https://discussions.flightaware.com/u/tgpopel)\
**Post date:** [November 16, 2022, 12:33pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/8 "2022-11-16T12:33:23Z")

</div>

I’m having issues as well using safari on my iPhone. I often have to click links multiple times or refresh to get pages to load. Cleared cache/cookies and it did not help.

---

<div class="post-metadata">

**Author:** ![mduell](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mduell/32/115680_2.png) [@mduell](https://discussions.flightaware.com/u/mduell)\
**Post date:** [November 16, 2022, 3:36pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/9 "2022-11-16T15:36:47Z")

</div>

Are any of you in the southern California region? One of our network providers was having some issues there overnight.

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/127232_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [November 16, 2022, 3:48pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/10 "2022-11-16T15:48:00Z")

</div>

I live in Southern CA and noticed I couldn’t get to my FlightAware stats page last night. Working ok now.

---

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 16, 2022, 3:51pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/11 "2022-11-16T15:51:08Z")

</div>

I am in South Africa

---

<div class="post-metadata">

**Author:** ![michaelgiebisch](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/michaelgiebisch/32/109122_2.png) [@michaelgiebisch](https://discussions.flightaware.com/u/michaelgiebisch)\
**Post date:** [November 16, 2022, 4:36pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/12 "2022-11-16T16:36:09Z")

</div>

I am located in Germany, problem continues

---

<div class="post-metadata">

**Author:** ![bebek](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/bebek/32/106557_2.png) [@bebek](https://discussions.flightaware.com/u/bebek)\
**Post date:** [November 16, 2022, 5:17pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/13 "2022-11-16T17:17:09Z")

</div>

Same here , kinda laggy slow respond , Ranking Database not loading allways , get Device error too says 14% of UDP data sent by Piaware not reaching Server (MLAT related).  
btw . Located in Europe , Austria  
Rpi3-Raspberry-Bullseye-Piaware 7.2  
my Guess The Server infrastructure is maxed out on side of FA

---

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 22, 2022, 8:01am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/14 "2022-11-22T08:01:31Z")

</div>

Update : As I am still having this issue of being unable to connect to FA (desktop PC, Win 10 Pro, Chrome, all at latest versions) on my PC hard-wired to a fibre line, I tried on my Laptop (Win 10 Pro, Chrome, all latest versions) via WiFi. Still could not connect. So I then tried my mobile phone (Galaxy S21 Ultra 5G) with WiFi off and connecting via 5G. No luck. So all 3 of my devices, using different connection methods, are unable to access the FA network. My phone says “This site can’t be reached. The web page https www flightaware com is either offline or has moved to a new address.”

Needless to say, this has become frustrating as I can no longer access my stats page, read squawks, or look at photos. Hopefully somebody at FA Staff will look into this with urgency.

---

<div class="post-metadata">

**Author:** ![oblivian](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/oblivian/32/135708_2.png) [@oblivian](https://discussions.flightaware.com/u/oblivian)\
**Post date:** [November 22, 2022, 10:12am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/15 "2022-11-22T10:12:56Z")

</div>

“The web page https www flightaware com is either offline or has moved to a new address”

Tried without www.  
You may not get the redirect served correctly. But the correct URL lacks.

---

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 22, 2022, 11:22am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/16 "2022-11-22T11:22:05Z")

</div>

Does not work. I put the www in my previous post in error.

---

<div class="post-metadata">

**Author:** ![adsbtech007](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/adsbtech007/32/122063_2.png) [@adsbtech007](https://discussions.flightaware.com/u/adsbtech007)\
**Post date:** [November 22, 2022, 11:58am UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/17 "2022-11-22T11:58:27Z")

</div>

I too have the same issue. In UK.

Have tried Chrome/Edge and Firefox. What is odd, If I clear cookies etc the page loads fine and I can access squawks, but as soon as I login I have issues accessing squawks, live data and mystats etc. So it does seem server related.  
The error I get is server reset connection.

---

<div class="post-metadata">

**Author:** ![tomvdhorst](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/tomvdhorst/32/136431_2.png) [@tomvdhorst](https://discussions.flightaware.com/u/tomvdhorst)\
**Post date:** [November 22, 2022, 7:11pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/18 "2022-11-22T19:11:10Z")

</div>

I’m getting prc\_reset\_connection\_errors now and then seems to be server related

---

<div class="post-metadata">

**Author:** ![VivPike](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/vivpike/32/136564_2.png) [@VivPike](https://discussions.flightaware.com/u/VivPike)\
**Post date:** [November 22, 2022, 7:40pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/19 "2022-11-22T19:40:22Z")

</div>

As long as our feeders are feeding, doesn’t matter to FA. No need for us to access FA to see our stats, track flights, read squawks, see pics, comments, etc. They have been very quiet on this issue. Disappointing, really.

---

<div class="post-metadata">

**Author:** ![tech0](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/tech0/32/113380_2.png) [@tech0](https://discussions.flightaware.com/u/tech0)\
**Post date:** [November 22, 2022, 9:31pm UTC](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368/20 "2022-11-22T21:31:51Z")

</div>

More than likely it is an issue with regional mirrors such as Cloudfare.  
I’ve had no issues in Florida.

[Next page](https://discussions.flightaware.com/t/unable-to-access-flightaware/85368.md?page=2)
