Fourteen million users — a meaningful fraction of them bots — hit Ticketmaster on November 15, 2022, generating more than 3.5 billion total system requests trying to buy tickets to a tour that had 1.5 million presale codes issued.1 The site did what any system built for ordinary demand does when hit with an order of magnitude more traffic than it was built for: it broke. Millions of fans sat frozen in paused queues, staring at a spinning wheel, some reaching the front of the line only to get an error message after the wait.1
Swift still sold 2.4 million tickets that day — a record.1 That number is worth holding next to the chaos it caused. The system genuinely failed at scale, and it also, in absolute terms, moved more tickets in a single day than almost any prior on-sale in history. Both facts are true simultaneously, and neither cancels the other out.
Ticketmaster's public response leaned hard into one specific frame: to meet the actual demand, a spokesperson said, Swift "would need to perform over 900 stadium shows (almost 20x the number of shows she is doing)... That's a stadium show every single night for the next 2.5 years."1 Translated out of corporate language: she's just too popular, this isn't on us.
That's a deflection — Ticketmaster's own platform genuinely buckled under the load, and "the demand was extraordinary" doesn't excuse a technical failure of this scale. But it's also, in a narrower sense, factually accurate: the fundamental mismatch here wasn't a fixable engineering problem. Demand for tickets to see Taylor Swift live, in 2022, genuinely dwarfed the physical number of seats that could ever be made available, at any price, through any platform, no matter how well it performed under load.
It's worth being precise about what actually capped supply, because it wasn't Ticketmaster's software. The Eras Tour was already Swift's biggest stadium tour — fifty-two dates in the first US leg alone, later expanded by a hundred more, mostly international.1 There were no bigger venues to move into. The tour's own logistics — days of setup and breakdown, roughly fifty semitrucks moving stage and equipment city to city — made adding meaningfully more dates structurally unfeasible on top of an already massive schedule.1 Ticketmaster's crash was real and its own fault. The underlying scarcity it crashed trying to manage was not a bug anyone could have coded away.
Fans, having lived through the failure, didn't just complain — they turned "breaking Ticketmaster" into a point of pride, a story about how popular their artist actually was.1 Politicians weighed in ("Buying guns should be harder than buying Taylor Swift tickets"). The general sale, initially planned for days later, got canceled outright, citing insufficient remaining inventory.1 The whole episode became known among fans as "The Great War," after a Midnights track title — folded directly into the tour's own mythology rather than remaining a separate embarrassment.
You're facing overwhelming demand for something with a genuinely fixed, physical supply ceiling, and the platform managing distribution is buckling under the load.
Separate the two problems before responding to either. One is a real technical and reputational failure — a platform that should have been stress-tested for a demand spike this predictable, given the artist's scale and history. The other is a structural mismatch no platform improvement could have solved, because the actual constraint (venue capacity, tour logistics, physical performance limits) sits entirely outside the ticketing system. Acknowledging both separately, rather than letting one excuse the other, is the only response that doesn't either unfairly blame the platform for physics or unfairly let the platform off the hook for its own failure.
The specific traffic numbers (14 million users, 3.5 billion requests, 2.4 million tickets sold, 52 initial dates plus 100 additional) are all directly reported and independently checkable. The tension: Ticketmaster's own framing (900 shows needed to meet demand) is presented in the book largely without independent scrutiny of Ticketmaster's own market position — the company controls a dominant share of major-venue ticketing specifically because of consolidation the book doesn't examine here, which is relevant context for assessing whether "we couldn't have prepared for this" is a fully honest account of a company with monopoly-adjacent market power.
The book treats Ticketmaster's deflection with more sympathy than a fuller account of the company's market dominance and history of technical failures at scale might warrant — the "we're just meeting extraordinary demand" framing conveniently omits Ticketmaster's own responsibility for building infrastructure capable of handling predictable spikes for an artist of Swift's demonstrated, well-known scale.
Below-Market Pricing as Trust Preservation — this fiasco and that page's pricing decision are two sides of the same underlying supply-demand mismatch; had dynamic pricing been used, the crash might have been less severe (higher prices reduce demand), but the trust cost documented on that page shows why avoiding dynamic pricing was still the more strategically sound choice despite this exact crash being a real, foreseeable cost of that decision.
Tour Logistics as a Hard Capacity Ceiling — this page names the visible, public failure; that page names the underlying physical constraint actually causing it. Reading them together separates a fixable technology problem from an unfixable physics problem, which the public conversation around this event mostly failed to do.
Sharpest implication: a platform failure and a genuine structural scarcity can occur in the same event without either one excusing the other — treating "extraordinary demand" as a full explanation for a technical collapse lets a dominant platform avoid accountability for infrastructure it should have built to handle predictable, well-telegraphed demand at this scale.
Generative questions: