Every Federal BOTS Act Case

Home › Guides › Federal BOTS Act Cases

✓ checked 19 October 2026 · sources: federal court records (CourtListener RECAP), FTC press releases, Public Law 114-274 · cases · tactics · method · download the data

The US government has filed 7 lawsuits under the Better Online Ticket Sales (BOTS) Act since the law took effect in December 2016, and 4 of them came in the 14 months from August 2025. The newest, filed on 15 October 2026, alleges that a ticket broker bought more than 18.5 million tickets by getting past ticket sellers’ purchase limits with thousands of accounts, IP proxy services and multi-session browsers. All 7 cases allege the use of proxy or masked IP addresses. On 28 September a federal judge ruled that the BOTS Act can apply to Ticketmaster itself, not only to brokers.

Everything this page says about what defendants did comes from complaints filed by the government. These are allegations. In the settled cases, the defendants neither admitted nor denied them, and the pending cases haven’t been decided.

7 federal BOTS Act cases4 since August 2025$42.4M in penalty judgments$4.0M actually paid

What the BOTS Act does

Congress passed the Better Online Ticket Sales Act of 2016 (Public Law 114-274, signed 14 December 2016) in response to ticket-buying software that can buy faster and in larger numbers than people can. It makes it unlawful to “circumvent a security measure, access control system, or other technological control or measure” that a ticket issuer uses to enforce posted ticket limits or purchasing rules. It also makes it unlawful to sell tickets obtained that way if the seller took part in, controlled or knew about the circumvention.

The law doesn’t ban reselling tickets, and it doesn’t ban bots as such. The question in each case is whether a buyer got around a technical control, such as a per-account limit, a CAPTCHA, or checks that link each purchase to a real person, card and IP address. A violation is treated as an unfair or deceptive practice under the FTC Act, which lets the government seek civil penalties. The FTC enforces the law, either itself or by referring cases to the Justice Department, and state attorneys general can sue too.

What changed: from three cases in four years to four in 14 months

For more than four years after the law passed, no federal case was filed. The first three came together on 14 January 2021, all in the Eastern District of New York against ticket brokers, and all settled within days. Then nothing for four and a half years.

On 31 March 2025, President Trump signed Executive Order 14254, which directs the FTC to “rigorously enforce” the BOTS Act and to work with state attorneys general on it. The FTC sued Key Investment Group in August 2025 and Live Nation and Ticketmaster in September 2025. It settled with Elite Events in July 2026, and the Justice Department sued REPS & Company on the FTC’s behalf on 15 October 2026.

The targets have also changed. The 2021 cases were about brokers using ticket bots and CAPTCHA-solving services. The recent ones describe large operations that use thousands of accounts, virtual credit card numbers, SIM banks for phone verification, multi-session browsers and proxy services, so that one buyer looks like thousands of separate fans. The Live Nation case goes further and targets the ticket seller itself.

Every federal BOTS Act case

FiledCaseCourt and docketDefendantWhat the complaint allegesStatus, 19 Oct 2026
14 Jan 2021United States v. Cartisim Corp.E.D.N.Y. 2:21-cv-00212Ticket broker and its ownerMore than 24,478 tickets from more than 9,088 Ticketmaster purchases since 2017Settled: stipulated order filed 15 Jan 2021; $4.4M penalty, $499,147 paid, rest suspended
14 Jan 2021United States v. Concert Specials, Inc.E.D.N.Y. 2:21-cv-00214Ticket broker and its ownerMore than 82,925 tickets from more than 34,513 Ticketmaster purchases since 2017Settled: consent judgment filed 19 Jan 2021; $16M penalty, $1,565,527 paid, rest suspended
14 Jan 2021United States v. Just in Time Tickets, Inc.E.D.N.Y. 2:21-cv-00215Ticket broker and its ownerMore than 48,451 tickets from more than 14,186 Ticketmaster purchases since 2017Settled: stipulated order filed 15 Jan 2021; $11.2M penalty, $1,642,659 paid, rest suspended
18 Aug 2025FTC v. Key Investment Group LLCD. Md. 1:25-cv-02716Ticket broker group and its officersAt least 379,776 Ticketmaster tickets costing nearly $57M (Nov 2022 to Dec 2023)Pending: in discovery (motions to compel referred to a magistrate judge, Sep–Oct 2026)
18 Sep 2025FTC v. Live Nation Entertainment, Inc.C.D. Cal. 2:25-cv-08884Ticket platform (Live Nation and Ticketmaster)Alleges Ticketmaster sold tickets that brokers bought over posted limits; $986M in resale fees 2019–2024Pending: motion to dismiss denied 28 Sep 2026; answer filed 13 Oct 2026
27 Jul 2026FTC v. Elite Events & Tickets LLCS.D. Ga. 1:26-cv-00142Ticket broker and its two owners86,869 tickets for 2,431 events where it bought more than the limit of eight (July 2022 onward)Settled: stipulated order filed 29 Jul 2026; $10,758,000 penalty, $300,000 paid, rest suspended
15 Oct 2026United States v. REPS & Company, Inc.S.D. Cal. 3:26-cv-05895Ticket broker and three officersMore than 18.5M tickets for at least 83,500 events, $1.3B spent, at least $120.8M profit (2022 onward)Pending: complaint filed 15 Oct 2026

Sources: complaints, orders and docket entries in CourtListener’s RECAP archive; for Elite Events, the FTC’s 27 July 2026 press release and complaint, because the complaint isn’t in RECAP. “DOJ for the FTC” means the Justice Department filed on referral from the FTC. Dollar amounts are as alleged or as ordered. Links to each source are in the CSV.

The four settled cases produced civil penalty judgments of $42.4 million. In each one most of the penalty was suspended on the basis of the defendants’ sworn financial statements, so the defendants actually paid $4.0 million, or 9.5%. The suspended amounts become due if the defendants’ financial statements turn out to be false.

What the complaints say the defendants did

Ticket sellers try to hold buyers to a per-event limit, often eight tickets, by checking that each purchase comes from a separate, verified person. According to the complaints, those checks look at the account, the payment card, the phone number and the IP address. Each tactic below is aimed at one of those checks.

Alleged tacticCartisimConcert SpecialsJust in TimeKey InvestmentLive NationElite EventsREPSCases
Proxy or masked IP addresses✓✓✓✓✓✓✓7
Many or fictitious accounts✓✓✓✓✓✓✓7
Ticket bots or purchasing software✓✓✓✓–––4
CAPTCHA bypass or solving✓✓✓––––3
Virtual credit card numbers–––✓–✓✓3
Multi-session browsers––––✓✓✓3
SIM banks–––✓✓–✓3
VPNs––––––✓1

✓ means the complaint (for Elite Events, the FTC’s summary of it) says the defendants used the tactic. In the Live Nation case, the complaint describes tactics used by brokers who bought on Ticketmaster, not by Live Nation itself. A dash means the tactic isn’t described, not that it wasn’t used.

  • Proxies and masked IP addresses (7 of 7 cases). The 2021 complaints say the brokers “used rotating proxy services and IP address blocks” to hide their real IP address from Ticketmaster. The REPS complaint alleges the use of “IP proxy services to utilize multiple IP addresses” and of VPNs, and says its purchasers got around a block that told them to disable a VPN. The Live Nation complaint says some broker software “generates proxy IP addresses so that it appears that each of the accounts is logged on from a different location”.
  • Many accounts (7 of 7). Every case describes buying through large numbers of accounts. According to the complaint, REPS signed agreements with employees and partners that let it open accounts in their names.
  • Multi-session browsers (3) and SIM banks (3). Multi-session browsers let one person run many logged-in accounts at once on one computer. SIM banks are devices holding dozens of SIM cards, so that each account can pass a text-message verification. Neither appears in the 2021 complaints.

The proxy and IP-address checks described in these complaints are the same ones that anti-bot services use on retail, travel and ticketing sites. For how widely such services are deployed, see the Anti-Bot Census. For how residential proxy networks get their IP addresses, including from infected devices, see the residential proxy botnet timeline.

The Ticketmaster ruling

The FTC and seven states (Colorado, Florida, Illinois, Nebraska, Tennessee, Utah and Virginia) sued Live Nation and Ticketmaster on 18 September 2025. Most of the case is about pricing. The BOTS Act count (Count III) relies on the second half of the law, which bars selling tickets that were bought by getting around the limits. The complaint alleges that Ticketmaster let brokers buy over its posted limits and then earned fees when those tickets were resold on its own platform.

Live Nation and Ticketmaster moved to dismiss. They argued that the law targets resellers, not platforms, and that a ticket limit on its own isn’t a technological measure. On 28 September 2026 Judge Maame Ewusi-Mensah Frimpong of the Central District of California denied the motion on every claim. She wrote that “The BOTS Act does not preclude platforms from facing liability, and the Court will not read it as doing so.” The order also says: “This Court is not deciding at this stage whether the FTC’s and the states’ accusations are true.” Live Nation and Ticketmaster filed their answer on 13 October, and the case is moving to discovery.

The newest case: REPS & Company

The REPS complaint was filed in the Southern District of California on 15 October 2026. It names the company, its CEO, its president and its chief operating officer. In its press release, the FTC says REPS bought more than eight tickets for “at least 83,500 events”, spent more than $1.3 billion on more than 18.5 million tickets, and made at least $120.8 million in profit reselling them. One paragraph of the complaint gives “at least 83,000 separate events” and another 83,500. The complaint says most of REPS’s purchasers are based in the Philippines. The FTC voted 2–0 to refer the case, and its release notes that “The case will be decided by the court.” On 19 October the docket in RECAP showed only the complaint and the summons.

  • Key Investment Group v. Ferguson (D. Md., 1:25-cv-02354). Key Investment Group sued the FTC and its commissioners in July 2025, challenging how the agency reads the BOTS Act and arguing the law is unconstitutionally vague. The court first denied the FTC’s motion to dismiss. On reconsideration, it dismissed the case without prejudice on 9 June 2026, noting that the company can raise the same challenge as a defence in the FTC’s enforcement case.
  • Key Investment Group v. Luján (D.D.C., 1:26-mc-00115). A motion, filed in August 2026, to compel Senators Ben Ray Luján and Marsha Blackburn to respond to subpoenas about how they understand the BOTS Act. The material was later filed on the Maryland enforcement docket, and the senators filed an opposition on 7 October.
  • Private suits. CourtListener also returns consumer class actions against Ticketmaster from 2018 and a 2025 racketeering suit by a concert promoter (Trident Concert Productions v. Ticketmaster) that mention the BOTS Act. The law gives the power to sue to the FTC and state attorneys general, so these suits rely on other laws.

For other court cases about bots, scraping and automated access, see the Scraping Law Hub.

State ticket-bot laws, 2025–2026

Added 20 October 2026. The federal BOTS Act is not the only ticket-bot law. States can pass their own, and many already have older bans on ticket-buying software. Since January 2025 the pace has picked up: we counted 45 bills with an action in 2025 or 2026 whose text bans or regulates ticket bots or software that gets around ticket-site controls. 43 are state bills, from 21 states plus the District of Columbia, and two are in Congress. 9 have become law: 4 in 2025 and 5 so far in 2026.

JurisdictionBillBecame lawWhat the bot provision does
IowaSF1466 June 2025Bans using or creating bots to buy event tickets; civil penalties
MaineLD91318 June 2025Adds bots (software that circumvents ticket-site security or access controls) to the state’s ticket resale law
OregonHB316724 June 2025Bars selling or using software that circumvents ticket-sale controls; now applies to “willful” rather than “intentional” conduct
MichiganSB015823 December 2025Event Online Ticket Sales Act: bans using a bot to buy event tickets online
OregonHB40245 March 2026Bans speculative ticket sales; the amended section keeps the ban on circumvention software
IllinoisSB031825 June 2026Prohibition on Bots Purchasing Tickets Act
North CarolinaS2577 July 2026Rewrites the ticket-sales article, defining a bot as software that bypasses ticket-site security
District of ColumbiaB26-022425 September 2026 (effective)Requires ticket sellers and resale sites to keep “reasonable technology” that stops software bypassing purchase limits
CaliforniaAB134927 September 2026Bans circumventing ticket-site security and using multiple IP addresses, accounts or email addresses to buy over a ticket limit

Dates are when the governor signed or approved the bill (Maine: approved 18 June 2025, Public Law chapter 354). The D.C. bill became D.C. Law L26-0181, effective 25 September 2026. Summaries are ours, from each bill’s enacted text.

Of the rest, 2 have passed one chamber (Delaware SB 181 and Michigan HB 4263), 7 failed or died when their session ended (in Florida, Oregon, Tennessee, Utah and Wisconsin), and 25 state bills were introduced with no further action recorded. New Jersey alone has 9, several of them identical bills filed in both chambers.

Many of these bills go further than the federal law. The BOTS Act bans getting around a ticket site’s security, but the newer state bills often name specific tactics. 17 of the 45 bills mention IP addresses. California’s new law, for example, makes it unlawful to use multiple IP addresses, multiple purchaser accounts or multiple email addresses to buy more tickets than a seller allows, a tactic several of the federal complaints above describe. The District of Columbia takes a different approach, putting a duty on the ticket sellers themselves to keep technology that stops bots.

In Congress, the MAIN Event Ticketing Act (H.R. 2713 and S. 196) would extend federal rules on ticket bots; the House committee ordered it reported on 16 September 2026. Separately, the TICKET Act would require the Federal Trade Commission to report on how it enforces the BOTS Act; we don’t count it above because it doesn’t change the rules on bots. For how these laws fit with scraping and access law more broadly, see our Scraping Law Hub; for the anti-bot systems ticket sites and others use, see the Anti-Bot Census.

How we counted. We searched LegiScan on 20 October 2026 for every bill with “ticket” in it in each state, D.C. and Congress, downloaded the latest text of each, and kept bills whose text bans or regulates ticket bots or circumvention software and that had an action in 2025 or 2026. We then read the matches by hand and dropped resolutions, renumbered duplicates and bills that only mention bots in passing. A bill can appear twice when the same text was filed in both chambers. Bill data is from LegiScan, licensed CC BY 4.0. The full list, with status and links, is in the CSV below.

Method

On 19 October 2026 we searched CourtListener’s RECAP archive for “Better Online Ticket Sales” (14 dockets), “BOTS Act” (25 dockets) and 15 U.S.C. § 45c with “ticket”. A case is included if the US government is the plaintiff and the complaint pleads a BOTS Act count; we checked each complaint by hand. We read the complaints and orders from RECAP and checked the Elite Events and REPS details against the FTC’s press releases. Federal court records and FTC releases are US government works. Cases brought only by state attorneys general in state court aren’t included.

Download the data

  • Federal BOTS Act cases (CSV): one row per case, with court, docket, alleged scale, status, penalties, the tactics each complaint alleges, and source links.
  • State ticket-bot bills, 2025–2026 (CSV): one row per bill, with status, last action, enactment details, whether it mentions IP addresses, and LegiScan and state links (20 October 2026).

Cite as: ProxyPicker, “Every Federal BOTS Act Case”, 19 October 2026, https://proxypicker.com/bots-act-ticket-bot-cases/. Data: CourtListener RECAP (Free Law Project); FTC.

Related: Scraping Law Hub · Anti-Bot Census · Residential proxy botnet timeline.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.