Proxies for Ryanair: The Airline That Took Screen Scrapers to Court

Ryanair is the airline that defined "screen scraper" as an insult. For more than a decade it has sued the agencies that resell its fares, built a verification wall for passengers who booked through the ones it has not approved, and fought the largest travel company in the world to a jury verdict over the scraping of ryanair.com. Proxies for Ryanair are therefore a narrower subject than for most travel sites: there is no point-of-sale pricing to chase, but there is one of the most defended airline websites in Europe, and a legal history any data team should read before it writes a line of code.

We run a proxy network, and Ryanair traffic reaches us from fare trackers, travel-data vendors and researchers studying low-cost carrier pricing. This is the practical page: the lawsuits and what they settled, the approved-OTA route and the verification wall, how Ryanair prices and in which currency, how the site blocks, which proxy type fits and how to size it. The sector background is in travel fare aggregation; the closest sibling, another airline that sued a scraper, is proxies for Southwest.

What proxies are best for Ryanair?

Rotating residential proxies behind a real browser for reading public fares, pinned to the departure market, and a static residential (ISP) exit held for the whole session for anything that touches a myRyanair account or the booking flow. Ryanair's bot management flags datacenter ranges and scripted clients early, so address quality matters more than address count. Mobile is the rare tier for runs nothing else survives; datacenter is for a manual check.

Ten years of Ryanair against the scrapers

Ryanair's position on scraping is a matter of record, and the record is long.

In January 2015 the Court of Justice of the European Union ruled in Ryanair v PR Aviation, a case about a Dutch fare-comparison site, that a database not protected by copyright or the database right can still be subject to contractual restrictions on its use, which is what Ryanair's website terms impose (CJEU, case C-30/14). That judgment is the legal foundation of every European airline's anti-scraping terms.

In 2020 Ryanair sued Booking Holdings in Delaware under the Computer Fraud and Abuse Act over the scraping of ryanair.com. In July 2024 a jury found for Ryanair, with loss set at exactly $5,000, the statute's minimum threshold. On 22 January 2025 the judge granted Booking.com judgment as a matter of law, ruling that Ryanair had not proven $5,000 of loss under the statute's definition; the court accepted only $2,457.72 of anti-bot technology expense as attributable (Technology & Marketing Law Blog). Ryanair appealed. The appeal ended when the two companies signed a partnership agreement on 26 August 2025 that put Ryanair flights on Booking.com, Kayak, Priceline and Agoda, with customers of those brands gaining access to their myRyanair account without completing Ryanair's customer verification (Booking Holdings).

The pattern in that timeline is the useful part. Ryanair does not object to distribution; it objects to distribution it has not approved, and it has been converting scrapers into partners one at a time. After loveholidays, it announced a deal with Kiwi.com on 29 January 2024 under which Kiwi gained direct access to the ryanair.com website without screenscraping and agreed to pass accurate customer contact and payment details to Ryanair (Ryanair). By August 2025 its approved list included loveholidays, lastminute, Travelfusion, Paxport, Kiwi.com, On the Beach, TUI, El Corte Inglés, Expedia and the Booking Holdings brands (Ryanair). If your business resells Ryanair, that is the door, and a proxy is not a substitute for it.

The verification wall

Ryanair's answer to unapproved agencies is aimed at their customers. Passengers who booked through what Ryanair calls OTA Pirates must complete a customer verification process before they can manage their booking, because Ryanair says those agencies screen-scrape the site and supply fake customer contact and payment details. Customers of approved partners skip it: the Kiwi.com announcement says plainly that Kiwi customers will no longer need to complete Ryanair's customer verification process which unauthorised OTA Pirates' customers must continue to do (Ryanair).

For a data team this is a warning about the shape of the site. Ryanair ties bookings to a myRyanair account, watches for bookings whose contact and payment details do not belong to the passenger, and has built an identity-check step specifically to break automated resale. Reading public fares is one thing. Anything that automates the booking flow is walking into a system designed to catch exactly that, and a proxy will not carry it through.

How Ryanair prices, and in which currency

There is no point-of-sale game to play on Ryanair. It is a point-to-point carrier that prices each route, and its terms state that fares, taxes, fees and charges must be paid in the currency of the country of the airport of departure, unless Ryanair specifies another currency at or before payment (Ryanair, terms and conditions, article 4). A flight from Berlin is quoted in euros, a flight from London in pounds. Ryanair offers to charge your card in your own currency at its own exchange rate, which consumer sites have criticised as unfavourable (The Travel Magazine), but that is a payment conversion, not a different fare.

So the market coverage argument that drives proxy choice on Skyscanner or Google Flights barely applies here. A fare tracker does not need an exit in every country. It needs addresses ryanair.com trusts, in enough quantity to spread a large search grid, ideally in the markets the routes depart from so that the visitor and the departure currency agree.

How Ryanair blocks you

Ryanair's site is one of the more heavily defended in European travel, which follows from everything above: a company that litigates scraping also invests in stopping it. Datacenter ranges and scripted clients draw challenges early, the booking flow is tied to accounts and identity checks, and Ryanair's own statements about detecting screen-scraped bookings by their contact and payment details show that detection continues after the request, into the data a booking carries. Your request has to look like a passenger's browser on a passenger's connection, and the more of the flow you automate, the less a proxy alone can do.

Which proxy type fits: residential, datacenter, ISP, or mobile

Datacenter proxies are cheap, fast and the first thing a defended airline site challenges. Use them for a manual look or for parser work on saved pages.

Rotating residential proxies are home connections drawn from a pool, one per search, rotated between. They pass the reputation checks that turn datacenter away and they spread a fare grid across enough addresses that no single one looks like a tracker. For public fare reads, this is the setup (background in what is a residential proxy).

ISP proxies are static residential addresses. A myRyanair account, a managed booking or any session that has to hold across pages needs one exit for the whole flow, and ISP is that exit.

Mobile proxies are carrier addresses shared by many phones, the last resort for runs that keep drawing challenges. Rarely needed for fare reads.

Free versus paid for Ryanair

A free proxy is a shared datacenter address that dies within minutes, and a defended airline site is where that profile fails first. For a one-off manual look at a route, our free proxy list and proxy checker are free and fine. For a tracker, paid residential is the floor; ours starts at $0.44/GB pay-as-you-go with no KYC, so a first run costs cents.

Setting it up

Use a real browser behind a residential exit for fare pages; our guides for Playwright and Puppeteer cover the wiring. Build search URLs directly rather than driving the search form, keep the cookies the site sets for the length of a session, and read prices in the departure currency the site chooses.

Rotate per search for public fares and hold a sticky ISP exit for anything logged in; the split is explained in rotating vs static residential proxies. Pin the exit to the departure country where you can, so the visitor and the quoted currency agree.

Stop at the fare. Do not automate the booking flow, do not enter contact or payment details that are not the passenger's, and do not build a resale product on scraped ryanair.com data without reading the cases above and the approved-partner route. That is not caution for its own sake; it is what the timeline says Ryanair will do.

How many IPs, and how fast

Ryanair's network is large and its fares move often, so the grid is big even for a modest tracker.

Sizing (rotating residential, one refresh cycle):
  searches/cycle = routes x departure dates
                 = 500 routes x 60 dates = 30,000 searches
  per search     = one rendered page; block images and fonts
  per address    = a few searches, then rotate

Refresh near-term dates daily, far dates weekly: the count halves.

Bandwidth is the bill. Trim the pages and refresh by distance, and our pricing, per gigabyte with no expiry, follows the tracker's real volume rather than a flat monthly fee.

Staying unblocked on Ryanair

• Home connection, real browser. A defended airline site scores both; fixing one leaves the other failing.
• One search per address, then rotate. No single IP should ever look like a tracker.
• Keep sessions honest. Cookies held within a session, dropped with the address; a fresh visitor every request is a bot tell.
• Match the departure market. Exit from the country the route departs from so the visitor and the currency agree.
• Pace like a passenger. Jitter the gaps and spread the schedule; the checklist is in avoiding IP bans while scraping.
• Read only. The moment a setup enters details or books, it is in the part of the site built to catch it.

The limits worth knowing

Proxies give a Ryanair fare read a trusted address and spread a tracker across enough of them that the site sees passengers. They do not change Ryanair's terms, they do not get a booking past the verification wall, and they do not stand in for the approved-partner route if you resell. Ryanair has spent a decade and two continents' worth of courts making that point.

For a manual look, our free proxy list and proxy checker are free. For a fare tracker, rotating residential at $0.44/GB pay-as-you-go behind a real browser, one search per address and pinned to the departure market, is what reads ryanair.com.

Sources

• Court of Justice of the European Union, Ryanair v PR Aviation, C-30/14, judgment of 15 January 2015.
• Technology & Marketing Law Blog, court overturns a bad jury verdict against scraping, Ryanair v. Booking, on the July 2024 verdict and the January 2025 ruling.
• Booking Holdings, Ryanair and Booking Holdings sign partnership agreement, 26 August 2025, and Ryanair, the same announcement, with the approved-OTA list.
• Ryanair, Ryanair agrees new partnership deal with OTA Kiwi.com, 29 January 2024, on screenscraping and customer verification.
• Ryanair, terms and conditions, article 4, on the currency of the departure airport.
• The Travel Magazine, Ryanair are inflating flight fares with currency exchange rates, on the payment conversion.