If paid in-flight Wi-Fi did not work, preserve the receipt and merchant, flight and aircraft details, connection times, portal status, error messages, and any crew or provider response. Run only a few reversible checks, distinguish a service outage from one blocked app or device problem, and request a refund with an accurate account of what was unavailable.

Key Takeaways:

Save the receipt, plan description, payment reference, and identity of the Wi-Fi provider.

Record when the service worked, failed, or was never available during the flight.

Capture errors without exposing passwords, card details, session tokens, or other passengers.

Test the portal and one neutral website before blaming a VPN or a specific app.

Report the failure while onboard when practical and retain the resulting case or acknowledgment.

This evidence workflow is part of a wider international travel preparation guide. For connection technique and VPN limitations, use the separate airplane Wi-Fi guide; this page focuses on proving what paid service you bought and received.

1. Record the purchase and service provider

Save the purchase confirmation before closing the portal. Record the plan name, promised scope, flight or time allowance, device limit, price and currency, transaction time, payment method, receipt number, and refund or support link. Keep the original email or downloadable receipt in addition to a screenshot.

Identify the merchant shown at checkout and on the payment record. The airline may advertise the service while a connectivity provider processes the purchase, or the airline may be the merchant of record. Save the portal domain and provider name without copying private session parameters from the address bar.

Capture the plan description as presented when you paid. “Full flight,” a time pass, messaging access, browsing access, and streaming access are different products. Do not claim the whole service was absent if only an excluded application failed; equally, do not reduce a flight-long outage to vague dissatisfaction.

Check whether the receipt is tied to a seat, flight, account, email address, voucher, or device. If you changed seats, aircraft, or flight after purchase, preserve the change notice. Do not repurchase repeatedly unless the provider instructs you in writing; multiple charges create a second payment problem.

2. Build a flight and session timeline

Record the date, origin, destination, airline, marketing and operating flight numbers, aircraft registration if visible, seat, and scheduled and actual departure times. Note when the crew announced that Wi-Fi should be available and any periods when the system was intentionally disabled.

Create a timeline with local or UTC time labels. Mark when you joined the onboard network, opened the captive portal, authenticated or redeemed the purchase, first loaded a neutral page, encountered each failure, contacted the crew, and stopped trying. A few precise intervals are more useful than “it never worked.”

Separate availability from quality. Record whether the network name was absent, connection to the local network failed, the portal did not open, payment succeeded but access did not activate, DNS or pages failed, only certain services were unavailable, or the connection repeatedly dropped. If some portion worked, state that duration honestly.

Preserve any onboard announcement or portal notice saying the service was unavailable, limited, or under maintenance. Write the wording and time rather than recording crew or passengers without permission. If the aircraft changed, compare the receipt's flight with the aircraft you actually boarded.

3. Capture useful errors without sensitive data

Take screenshots of the portal status, plan activation, error code, network settings needed to identify the onboard network, and a failed neutral page. Include the device clock where it helps establish sequence. Crop out notifications, personal messages, full email addresses, booking references, loyalty numbers, and nearby passengers.

Do not capture or share a password, one-time code, payment-card number, security code, authentication cookie, QR token, or the complete portal URL if it contains a session identifier. A support team normally needs the receipt, flight, approximate time, device type, and visible error—not control of your account.

Write the device model, operating-system version, browser, and whether private addressing, relay, custom DNS, firewall, VPN, or content filtering was enabled. This is diagnostic context, not an instruction to disable every protection. If you change one setting, record the before-and-after result and restore your preferred security state afterward.

Save the evidence offline. Cloud upload may fail for the same reason as the service. Use a small folder containing the receipt, timeline, screenshots, and a text note; give files neutral names and remove information unrelated to the claim before submission.

4. Run minimal checks to classify the failure

Confirm airplane mode remains on and Wi-Fi is permitted, then forget and rejoin only the official onboard network named by the airline. Open the provider's stated portal address or a plain browser window. Do not join look-alike networks, bypass certificate warnings, install an unknown profile, or weaken device security to force access.

Test one neutral lightweight website and the local portal before testing an app. If the portal works but a work service, streaming site, call, or VPN does not, the purchased plan or onboard network may restrict that traffic. Record the distinction rather than calling it a total outage.

Temporarily pause a VPN only if the airline or provider's documented connection steps require portal sign-in first and you are comfortable doing so. Re-enable protection after authentication if the plan permits it. A captive portal, satellite link, route policy, app outage, and device configuration can produce similar symptoms, so change one variable at a time.

Try one approved second browser or device only when the plan allows it. Record whether the purchase was locked to the first device and whether transferring access is supported. Do not evade a device limit or share a voucher contrary to the plan. Stop after a small reproducible test set; endless retries can erase useful error state and consume the flight.

5. Report that paid in-flight Wi-Fi did not work and keep the acknowledgment

Tell cabin crew that a paid service is unavailable and ask whether the aircraft has a known outage. Crew may not control billing or repair the system, but an onboard report can establish that the problem was raised during the flight. Record the time and any neutral acknowledgment; do not demand personal staff details they cannot provide.

Use the provider's onboard support channel if it loads. Give the receipt number, flight, seat if requested, device and operating system, approximate failure interval, and error code. Ask for a case number or transcript. If chat vanishes when the flight ends, capture the closing screen first.

After landing, use the official support or refund route from the receipt or airline website. Describe whether access never activated, worked only for part of the purchased period, or failed for a specific excluded service. Attach a short evidence index rather than every screenshot by default.

Under US DOT consumer guidance, Wi-Fi is an ancillary air-travel service and fees are refundable when the service was unavailable through no fault of the consumer.［1］ The rule's scope and the distinction between unavailable service and consumer non-use matter; it is not a worldwide promise for every quality complaint.

6. Request the correct remedy and track it

Ask the merchant or responsible provider for the remedy supported by the purchase terms and applicable law. State the amount, currency, payment reference, service promised, portion unavailable, troubleshooting performed, onboard report, and requested outcome. Keep the request factual and do not inflate a slow connection into a complete outage.

Airline and provider refund routes differ. United, for example, directs customers to its refund process for paid services they did not receive, while Delta's onboard Wi-Fi page routes purchased Wi-Fi concerns to the relevant support path.［2］［3］ These are company-specific examples, not rules for another carrier.

Save the case number, submission date, promised processing step, refund reference, and final response. Distinguish a provider-approved refund from a posted account credit. If the merchant refuses or misses its commitment, ask your payment issuer about the accurate dispute category and evidence; the authorized-purchase dispute guide explains that separate process.

Avoid double recovery. Tell an insurer or card issuer about any provider refund or voucher, and check the actual policy before making a claim. The travel-claim evidence guide can help organize receipts, but ordinary connectivity disappointment may not be an insured event.

Summary

Preserve the plan description, merchant, receipt, and payment reference at purchase time.
Build a flight and session timeline that distinguishes no service, partial service, and app-specific failure.
Capture reproducible errors while removing credentials and unrelated personal data.
Perform a small, reversible diagnostic set and report the issue while onboard when practical.
Request the remedy from the correct merchant and track approval separately from posted credit.

Frequently Asked Questions

What screenshot best proves in-flight Wi-Fi failed?

Capture the activated plan or receipt, visible error or portal status, and device time. Pair screenshots with the flight and session timeline; one generic “offline” icon rarely proves which service failed.

Should I turn off my VPN to test airplane Wi-Fi?

Only when the provider's official steps require portal authentication first and you choose to do so. Record the result, re-enable protection afterward, and do not assume a VPN is the cause merely because one app fails.

What if Wi-Fi worked for only part of the flight?

Record the working and unavailable intervals accurately. The remedy may depend on the plan, merchant, applicable rules, and whether partial provision satisfied the purchased service.

Who should refund airline Wi-Fi?

Start with the merchant and support route on the receipt. The airline, ticket agent, or connectivity provider may have different roles, so keep the checkout and payment records.

Is slow in-flight Wi-Fi the same as unavailable Wi-Fi?

Not automatically. Save any advertised limitation and test result, but distinguish poor quality from a service that never activated or could not be used for its stated scope.

When should I dispute the card charge?

First request the appropriate remedy from the merchant unless an issuer deadline requires faster action. If escalation is necessary, describe the authorized purchase and service failure accurately and disclose any refund already received.

Can a VPN repair broken in-flight Wi-Fi?

No. A VPN needs a working underlying connection and cannot repair aircraft equipment, satellite capacity, the captive portal, or a provider account.

When can a VPN affect activation of purchased Wi-Fi?

An active VPN can interfere with the captive-portal step that attaches your paid pass to the onboard session. If the provider’s documented steps call for it, pause the VPN, finish authentication on the verified portal, and record whether the purchase now activates. This distinguishes a portal problem from an unavailable aircraft internet link. Once the underlying service works and the plan permits VPN use, connect AethoVPN and test the protected connection; if it is not set up yet, start the 3-day free trial before your flight. A VPN cannot activate the purchase for you, increase satellite capacity, determine refund eligibility, or make a provider pay.

References

U.S. Department of Transportation, “Refunds” — https://www.transportation.gov/individuals/aviation-consumer-protection/refunds
United Airlines, “Refunds” — https://www.united.com/en/us/refunds/
Delta Air Lines, “Onboard Wi-Fi” — https://www.delta.com/us/en/onboard/inflight-entertainment/onboard-wifi

Sources checked 6 September 2026.

This article provides general technical and record-keeping information, not legal, financial, or aviation advice. Service terms, refund rights, and dispute deadlines depend on the provider, itinerary, payment method, and jurisdiction.

Related reading:

Paid In-Flight Wi-Fi Did Not Work: What Evidence to Keep