Melbourne Cup Meltdown : How a Betting System Crashed at the Worst Possible Moment
About this episode
Every year, the Melbourne Cup pushes Australia's betting infrastructure to its limits. In 1991, a known software bug turned one of the busiest days of the year into an IT disaster. As millions of bets poured in, CPU utilisation unexpectedly collapsed and the betting system ground to a halt at the worst possible moment.
Jack Smith is joined by veteran mainframe specialist Neale to revisit the incident, explain why the bug had been accepted for so long, how the team recovered, and what modern IT professionals can learn about technical debt, capacity planning, and the risks of carrying known defects into critical production systems.
Want even more info ? Read our show notes and related blog post related to this episode : https://blog.ithorrorstories.eu/episode-19-melbourne-cup-meltdown/
00:00 Introduction
00:53 Mainframe Basics
02:01 Melbourne Cup Explained
05:01 System Failure
09:06 Aftermath & Reflection
17:03 Learning from Errors
21:53 Modern Vs. Past Tech
29:51 Conclusion
Get every episode summarized
Each time IT Horror Stories with Jack Smith publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from IT Horror Stories with Jack Smith
Jack's Rants - Why You Need to Reboot : Why Rebooting Your Computer Actually Fix...
IT Horror Stories with Jack Smith
Testing Software Properly : Software Testing Done Right – Where, When and What S...
IT Horror Stories with Jack Smith
Microcode Mayhem : How a Mainframe Timer Bug Slowed an Entire Development Team
IT Horror Stories with Jack Smith
Jack's Rants - AI Is The New Shadow IT : Why Employees Are Quietly Building the...
IT Horror Stories with Jack Smith