Anyone having issues with American Airlines wifi lately?

Wifi
1

I’ve had unreliable wifi on several recent American Airlines flights, even after paying for the full flight pass. The connection keeps dropping and streaming or working remotely becomes impossible. Is this a common issue, and does anyone know reliable fixes, refunds, or better ways to connect on AA flights?

2

Yeah, AA wifi has been rough lately. You are not imagining it.

What I have seen across the last 6 or 7 AA flights:

  1. Different hardware on different planes

    • Older A319 and some 737s with Gogo or older Viasat drop a lot, especially during climb and descent.
    • Newer planes with Viasat tend to work better, but even those stall when a lot of people stream.
    • If the portal says “satellite connection unstable” or you see long DNS lookup times, it is usually a network load issue, not your device.

  2. Time of day and route matter

    • Peak business routes like DFW–LGA, CLT–BOS, LAX–JFK often crawl during weekday mornings and late afternoons.
    • I get more stable speeds on mid day flights and on leisure routes.
    • My rough speed tests: anywhere from 0.5 Mbps up to 15 Mbps, wildly inconsistent on the same route, same plane type.

  3. Refunds and credits

    • Use the “Contact American” form after the flight, pick “Inflight WiFi” and include flight number, date, and a short note like “wifi kept dropping, could not keep a VPN or Zoom call up.”
    • I have gotten refunds or vouchers for about 70% of the complaints. Not instant, but they respond within a week for me.
    • If you bought it through the AA inflight portal with your AAdvantage login, they usually see the purchase on their side, so your odds are better.

  4. What you can do on your side

    • Turn off VPN if you can. AA wifi hates some VPNs, especially on Zoom or Teams.
    • Force your device to use 5 GHz wifi, not 2.4 GHz, if the onboard router broadcasts both.
    • Disable automatic cloud sync and large downloads. iCloud, OneDrive, and Steam updates can eat your bandwidth without you noticing.
    • For work, stick to email, Slack, light web browsing. Video calls often drop unless you are on a light flight and a newer Viasat bird.
    • If the portal lets you run a speed test, screenshot it. Helps when you request a refund.

  5. If you want to troubleshoot your own setup
    When wifi is flaky, it is sometimes a mix of the plane network and your own laptop wifi settings. At home or in the office, you can test and tune your wifi so you know your device behaves well before you fly. A tool like NetSpot wifi analyzer and survey tool helps you map signal strength, channel congestion, and dead zones. That does not fix AA’s satellite, but it helps you rule out your own config and gives you a cleaner baseline.

  6. Patterns I have noticed

    • More drops near heavy weather, especially over the Midwest.
    • Shorter flights get less consistent service, probably less time in the “sweet spot” for satellite coverage.
    • When the crew announces “wifi might not be available the entire flight,” assume it will be bad and do offline work.

So yes, it is a common thing, especially on certain aircraft and routes. If you need reliable remote work, plan for offline tasks and treat working wifi as a bonus. I still pay for it on longer flights, but I screenshot speeds, keep my expectations low, and ask for refunds when it is unusable.

3

Same boat here. AA wifi has been sketchy for me the last ~6 months, so yeah, you’re definitely not the only one.

I mostly agree with what @nachtdromer wrote, but I’ll slightly push back on one thing: for me it has not just been “older planes.” I’ve had two brand‑newish Viasat 737 MAX flights where speeds started decent, then completely cratered after about 45 minutes, even though the cabin wasn’t full and the portal showed “good” coverage. So I think AA’s traffic shaping or backhaul is part of the mess, not just hardware age or load.

A few angles that haven’t been mentioned yet:

  1. Monthly pass vs flight pass
    If you’re flying AA more than a couple times a month, the monthly Gogo / AA plan (when available on your routes) spreads the risk. I stopped buying single flight passes precisely because of what you described. Mentally it hurts less when the connection tanks on one leg if I’ve already “amortized” the cost across several flights.

  2. Expectations by use case
    Streaming and remote desktop are basically edge cases on AA lately. I treat the wifi as:

  • Reliable enough for basic email and text chat most of the time
  • Hit or miss for large attachments, VPN, Git pulls, and anything “live” like Zoom
    If I absolutely must be on a video call, I now assume it will fail and plan an audio‑only dial in from my phone as backup.
  1. Device side tweaks that are a bit more “advanced”
    Without repeating the basics:
  • Manually set your DNS to something like 1.1.1.1 or 8.8.8.8 after the captive portal is done. AA’s DNS sometimes freaks out, which looks like “no wifi” even when signal is fine.
  • Disable “Wi‑Fi calling” on your phone. I have had multiple instances where that feature fought with the captive portal and killed the connection for everything.
  • On laptops, kill background containers / dev tools. Docker, package managers, and cloud IDEs can quietly hog bandwidth and trigger throttling.
  1. Planning your work around AA wifi
    What helped my sanity:
  • Before the trip, sync everything locally in OneDrive / Dropbox / Google Drive so you can work offline if the inflight network chokes.
  • Queue up docs, emails to draft, slide decks to edit. Treat inflight time as “offline deep work” first, “online bonus” second.
  • Download streaming content to your device in advance. Relying on AA wifi for Netflix or YouTube is basically rolling dice.
  1. When to complain and how specific to be
    Instead of just “wifi didn’t work,” I’ve had better luck with:
  • “Could not load standard web pages like gmail.com and outlook.office.com for most of the flight”
  • “Speed stayed under 0.2 Mbps for more than an hour, pages timing out”
  • Mention if the portal itself was slow or unreachable.
    I also attach a quick screenshot of speedtest or even the browser error page. Like @nachtdromer said, refunds are hit or miss, but being concrete seems to help.
  1. Ruling out your own setup
    AA absolutely has issues, but sometimes a flaky device makes it worse. At home I used NetSpot to map my wifi and fix some weird roaming and channel problems, and that actually made my laptop behave better on any network, including planes. If you want to clean up your own config before flying, a survey/analyzer like improving your Wi‑Fi stability and coverage can at least remove the “is it my laptop?” question from the equation.

Short version: yes, it’s common, it’s inconsistent even on “good” aircraft, and AA wifi right now is something I treat as a convenience, not infrastructure I can rely on. If you need rock‑solid connectivity for work, I’d plan as if it will not be there and be pleasantly surprised on the flights where it actually behaves.

6 Likes
4

Short version: yes, AA wifi has been weirdly unreliable lately, and not just on the routes others mentioned.

A few angles that complement what @sognonotturno and @nachtdromer already covered:

1. It is not always “congestion” or “hardware”

They are right that load and aircraft type matter, but I have had flights where:

  • Cabin was half empty
  • Portal said “good” connection
  • Basic sites like Fastmail and GitHub kept timing out while Speedtest showed 5–8 Mbps

That smells more like aggressive traffic shaping and flaky DNS than pure capacity. In particular, long‑lived connections such as SSH, RDP, certain video platforms, and some gaming protocols get nuked while casual browsing still works. So if your use case leans on persistent sessions, AA wifi will feel reliably bad even when raw throughput is OK.

2. Do not overestimate “monthly pass spreads the risk”

I slightly disagree with the idea that a monthly pass makes the pain go away. It only really helps if:

  • You fly AA a lot, and
  • Most of those flights are on the same provider mix covered by that pass

If your travel pattern is mixed (AA plus others, or lots of short hops) you can end up with a month of terrible value instead of one annoying but contained flight pass. In that case, sticking to single‑flight purchases and aggressively requesting refunds can actually be more rational.

3. Diagnose at home so you know what is not your fault

You cannot fix AA’s satellite or their backend, but you can remove variables on your side before you ever board:

  • Test how your laptop behaves when roaming between access points, how it handles captive portals, and whether it recovers well from brief drops.
  • Tools like NetSpot are handy for this at home or the office: they let you visualize signal strength, channel overlap, and roaming behavior.

Pros of NetSpot in this context:

  • Clear heatmaps so you can see where your own wifi is actually bad
  • Good for uncovering driver quirks and sticky roaming tendencies on your device
  • Helps you standardize your wifi settings so you are not debugging your laptop at 35,000 feet

Cons:

  • It will not change anything about AA’s satellite link or traffic shaping
  • There is a learning curve if you dig into the survey features
  • Some advanced options are overkill if you just want a quick yes/no check

The point is not that NetSpot magically fixes inflight wifi. It just means that when AA’s network acts up, you can be far more confident the fault is not your own configuration.

4. Treat “portal works, internet does not” as a distinct failure mode

One thing I see a lot on AA:

  • Portal loads fine
  • Messaging or cached pages seem OK for a bit
  • Anything that needs fresh DNS resolution just dies

When that happens, classic tips like toggling airplane mode or forgetting the network do not always help. A slightly different approach:

  • Try a low‑overhead site first, like a simple text‑heavy news page
  • If the portal still responds but outside sites stall for more than 10–15 minutes, mentally write off that flight’s connectivity instead of spending half the leg rebooting devices

At that point you are fighting their infrastructure, not your laptop.

5. Plan connectivity as “tiers” of reliability

Instead of thinking “wifi works” or “wifi does not,” I plan AA flights in tiers:

  • Tier 1: Email, chat, text‑only web. Usually OK.
  • Tier 2: File sync, large attachments, code pulls. Works maybe half the time.
  • Tier 3: Real time stuff like Zoom, RDP, cloud IDEs, trading dashboards. Assume it will fail.

If your critical task lives in tier 3, do what @nachtdromer hinted at and build a backup that does not rely on AA at all, such as phone dial in or a plan to do async updates instead of live calls.

6. When you complain, separate device issues from network issues

To add to their refund tips, I have had more success when I clearly differentiate:

  • “Signal / portal kept dropping” versus
  • “Signal and portal fine, but internet unusable for X minutes / Y portion of flight”

The latter points directly at AA’s network stack, which is harder for them to pin on passenger devices. Attach one or two concise screenshots if you have them, but do not flood them with logs.

So yes, what you are seeing is common, and it is not just you. Between what @sognonotturno and @nachtdromer shared and some basic baseline testing with something like NetSpot on your own gear, you can at least reclaim some sanity and know when it is time to stop troubleshooting and just switch to offline work.