Ticketmaster alleged dynamic pricing caused large Oasis ticket price jumps in 2024

Public complaints after the Oasis ticket sale in September 2024 led the CMA to open an investigation into Ticketmaster’s use of dynamic and tiered pricing and the transparency of price information provided during online queues. The DOJ’s May 2024 antitrust complaint against Live Nation and Ticketmaster raised broader competition concerns. The CMA later secured undertakings from Ticketmaster to improve disclosures while noting it had not found evidence that algorithmic dynamic pricing was used in that specific sale.

Ticketmaster · Incident Sep 5, 2024 · Indexed Jun 9, 2026 · 4 sources

Opaque tiered or dynamic pricing and insufficient queue disclosures led to sudden, large price jumps for fans.
What
Public complaints after the Oasis ticket sale in September 2024 led the CMA to open an investigation into Ticketmaster’s use of dynamic and tiered pricing and the transparency of price information provided during online queues.
Incident date
Sep 5, 2024
Who
Ticketmaster
Failure mode
Policy Violation
AI surface
Algorithmic Decision
Severity
High

What happened

In September 2024 fans and media reported that prices for Oasis tickets on Ticketmaster rose sharply while buyers waited in online queues, with some buyers seeing prices multiply several times over initial prices. The U.K. Competition and Markets Authority launched an investigation into Ticketmaster’s use of dynamic or tiered pricing on 5 September 2024. The U.S. Department of Justice filed a broader antitrust lawsuit against Live Nation and Ticketmaster on May 23, 2024 which referenced long‑running concerns about pricing and market power.

What broke inside the model

Failure path · mode profile · Policy Violation
  1. 01 · TriggerA prompt pushes against a deployment boundary.
  2. 02 · Model stepThe model produces the disallowed output.
  3. 03 · Control gapNo enforcement blocks it at generation time.
  4. 04 · FailureThe output crosses the policy line.
  5. 05 · ConsequenceA limit the business set is breached in public.

The output crosses a policy boundary the deployment had defined.

The reported failure involved pricing systems and sales workflows that applied tiered or dynamic price changes without sufficiently clear, timely disclosures to buyers, and queue interfaces that did not communicate price ranges or when cheaper tiers had sold out. Regulators focused on transparency and labelling failures such as use of ‘platinum’ labels and lack of queue updates rather than concluding there was confirmed algorithmic misconduct in the Oasis sale.

Public visibilityHigh
Regulatory exposureActive
Customer impactMany customers
Financial impactUnknown
Time to disclosureDays
  1. PrimaryJustice Department Sues Live Nation-Ticketmaster for Monopolizing Markets Across the Live Concert Industryjustice.gov
  2. PressTicketmaster 'dynamic pricing' subject to U.K. investigation into Oasis ticket salesnpr.org
  3. PrimaryCMA secures changes from Ticketmaster following Oasis tickets investigationgov.uk
  4. PressDynamic Pricing under scrutiny: don’t look back in angerhausfeld.com
Permalinkhttps://failureindex.ai/failures/ticketmaster-alleged-dynamic-pricing-caused-large
CitationAI Failure Index. "Ticketmaster alleged dynamic pricing caused large Oasis ticket price jumps in 2024" (FI-0342). Realm Labs. https://failureindex.ai/failures/ticketmaster-alleged-dynamic-pricing-caused-large (indexed Jun 9, 2026).
Share cardA branded image of this record for posts and slides.

Data fields CC-BY 4.0, prose citation permitted. Incident ID FI-0342. Full dataset at /data.

Note from Realm Labs, the Index steward

How Realm fits

Controls for this failure mode
  • Prism
  • OmniGuard

This entry sits in the index's predictive wing: a system that scores, ranks, perceives, or steers rather than generates. Realm's runtime layer is built for the generative and agentic systems now moving into these same decision seats, where it watches a model's internal state and holds an unsupported claim or an unchecked action before it commits. The control gap on this record, an automated decision that reached people with no runtime check in front of it, is the same gap. The index keeps predictive failures on the record because the pattern carries straight into the systems shipping today.