Empires Before The Fall

Empires Before The Fall

Download on the App Store

Empires Before The Fall episodes

  • The crown taken from Anuradhapura that emptied the island's kingship
    A king stole a rival crown and emptied Anuradhapura-then the island’s kingship never returned. What did that crown do to power?

    The crown taken from Anuradhapura that emptied the island's kingship

    In this episode, we follow the fall of Anuradhapura, the Chola occupation, and the peculiar disappearance of the island’s royal center. We trace who moved crowns, who fled, and which decisions reshaped where rulers sat - and ask why no Sinhalese king rebuilt the old capital.

    Person: Rajaraja I
    Person: Mahinda V
    Date: 993
    Location: Anuradhapura, Sri Lanka
    Event: Chola invasion and occupation

    - A Chola army crossed the Palk Strait in 993, burned Anuradhapura, and established a lasting provincial administration.
    - Decades earlier, Pandya royal regalia - crowns and insignia - had been transported to Anuradhapura, then allied with local powers.
    - Mahinda V, king since 981, lost control after Tamil mercenary troops revolted and fled south to Rohana before the invasion.
    - The Cholas renamed towns, built temples, and made Polonnaruwa their administrative center rather than treating the raid as temporary.
    - Around 1017-1018 Rajendra I captured Mahinda V, his queen and daughter, and loaded the island’s royal regalia onto ships bound for India.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    17 min
  • The Orkhon inscriptions asked where the qaghan went - the vassals answered
    A severed khagan’s head is sent to Chang'an by Uyghur riders in 744, and the Orkhon inscriptions ask where the qaghan went - who answered them?

    The Orkhon inscriptions asked where the qaghan went - the vassals answered

    In this episode, we trace the collapse of the Second Turkic Khaganate from Ilterish Qaghan’s rise with two hundred men to the internal unraveling that sent Ozmish Qaghan’s head south. The episode follows the record carved in the Orkhon inscriptions and asks what broke inside an empire that once spanned from Lake Baikal to the Syr Darya.

    Person: Ozmish Qaghan
    Person: Ilterish Qaghan
    Date: 744
    Location: Ötüken; Chang'an; Orkhon River
    Event: Severed head transported to Chang'an; Orkhon inscriptions asking “Where is my qaghan?”

    - Ilterish Qaghan rebuilt the khaganate starting in 683 with only two hundred men and launched forty-seven documented campaigns within a decade.
    - The Tang dynasty had managed Turkic groups through frontier settlement and public displays of domination, including the market execution of fifty-two Turkic leaders in 681.
    - The Orkhon inscriptions, raised in the early 800s, preserve carved questions and angry testimony about decades of Tang administration and subjugation.
    - In 744 Uyghur riders carried Ozmish Qaghan’s severed head in a box toward Chang'an after burning the last capital of the Second Turkic Khaganate.
    - The collapse in 744 was driven by Turkic vassals-Basmyls, Karluks, Uyghurs-dismembering the khaganate rather than by a Tang military conquest.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    21 min
  • The commander who killed the emperor's son and then stopped the march
    A Roman commander killed the emperor’s son at Cologne, declared a rival Gallic Empire - so what happened next?

    The commander who killed the emperor's son and then stopped the march

    In this episode, we trace the moment a Rhine frontier commander executed Saloninus and the praetorian prefect, declared a separate Gallic state, and then halted his advance on the heart of the empire. What did his actions do to Rome’s authority, and why did the legitimate emperor largely abandon efforts to retake the breakaway realm?

    Person: Marcus Cassianius Latinius Postumus
    Person: Saloninus
    Date: Autumn of 260 CE
    Location: Colonia Agrippina (modern Cologne) and the Rhine frontier
    Event: Founding of the Gallic Empire and the Battle of Empel

    - Postumus killed Saloninus and the praetorian prefect Silvanus at Cologne, then proclaimed himself emperor in Gaul.
    - He organized Roman-style institutions: minted coins claiming five consulships and likely convened a senate in Augusta Treverorum.
    - Within months his forces won at Empel, after which the Rhine frontier experienced roughly ten years of relative peace.
    - Gallienus launched one serious campaign against Postumus in 263 CE, which failed, and then did not mount further large-scale efforts to reclaim Gaul.
    - Despite being a usurper, Postumus sustained taxation, coin circulation, and administrative functions across Gaul, Germania, and Britannia.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    23 min
  • The Shenandoah's newspapers stayed unread - it kept burning ships
    A Confederate raider in the Arctic, cut off by distance and news, keeps hunting Union whalers months after the Civil War ends.

    The Shenandoah's newspapers stayed unread - it kept burning ships

    In this episode we trace how a single Confederate warship, isolated in the Pacific and Arctic, continued to operate on orders given months earlier. We follow Captain James Waddell, his officers, and the chain-of-command logic that pushed the CSS Shenandoah into the North Pacific whaling fleet - so what decisions did they make when the world around them had already changed?

    Person: Captain James Waddell
    Ship: CSS Shenandoah (formerly Sea King)
    Date: June 22, 1865
    Location: North Pacific / Arctic Ocean
    Orders: Sail to the Pacific and destroy Union whaling fleets

    - October 19, 1864: Sea King transferred to Confederate command, armed, and renamed Shenandoah with Waddell in command.
    - Shenandoah ordered to operate entirely outside the Atlantic, attacking Union commerce and the New England whaling economy.
    - Lack of communication: no telegraph or radio across the Pacific meant Waddell relied on newspapers, letters, and ship testimony for news.
    - By April 9, 1865 Shenandoah was anchored at Ponape with thirteen prizes taken, unaware of Appomattox and the Confederacy’s collapse.
    - June 22, 1865: operating under standing orders and military logic, Waddell encountered the Arctic whaling fleet and opened fire.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    18 min
  • The CT scan that split Ramesses III's throat upended his death story
    A CT scan of Ramesses III’s mummy revealed a throat wound inside his palace - what actually happened?

    The CT scan that split Ramesses III's throat upended his death story

    In this episode, we follow how a routine scan and a century of untouched bandages forced experts to reconsider how Ramesses III died. We trace the pharaoh’s military triumphs, the growing unrest inside his court, and the clues that link a palace conspiracy to the wound on the mummy - but what did the scan really mean for his final moments?

    Person: Ramesses III
    Date: CT scan winter 2011; BMJ publication December 2012
    Location: Ramesses III’s mummy (museum), Medinet Habu (mortuary temple)
    Event: CT scan revealing deep neck cut severing trachea and major vessels
    Case: Judicial Papyrus of Turin naming conspirators including Tiye and Pebekkamen

    - A CT image showed a deliberate, single cut nearly to the spine hidden under original embalming bandages.
    - Radiologists Ashraf Selim and Sahar Saleem led the forensic team that published the findings in the British Medical Journal.
    - Ramesses III had defended Egypt from Libyans and the Sea Peoples and built Medinet Habu as a fortified mortuary temple.
    - Court records list a conspiracy including a secondary wife named Tiye, chamber chief Pebekkamen, and servants with access to the pharaoh’s food.
    - The embalming included an amulet placement, and earlier examinations had never unwrapped the bandages that concealed the wound.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    21 min
  • The 1998 spike misled everyone - a single El Niño froze the debate
    A single 1998 El Niño spike became the anchor for years of debate-had global warming stopped?

    The 1998 spike misled everyone - a single El Niño froze the debate

    In this episode, we lay out how one anomalous year and the choices about where to start measuring temperatures redirected public and institutional conversation about climate risk. What happened in 1998, and why did that single El Niño become the measuring stick for fifteen years of debate?

    Year: 1998
    Event: Strongest El Niño of the century (1997-1998)
    Finding: 1998 recorded the hottest year in the instrumental record
    Report: NOAA study (April 2009) showed trends depend on start year choice
    Observation: WMO (March 2014) reported >90% of excess energy stored in oceans

    - The 1997-1998 El Niño released an extraordinary pulse of heat from the Pacific, producing a surface-temperature spike that stood far above the trend line.
    - Many researchers and commentators used 1998 as the starting point for trend calculations, effectively measuring warming from a statistical outlier.
    - NOAA demonstrated that starting the trend in 1998 versus 1999 produced opposite conclusions about whether surface warming continued.
    - Media and opinion pieces from 2006-2008 amplified the “hiatus” narrative, with claims of halted warming entering public discourse despite scientific rebuttals.
    - Beneath the surface, oceans absorbed the vast majority of heat between 2000 and 2013, a redistribution of energy that surface thermometers alone did not capture.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    16 min
  • The rain that fed twentyfold mouse booms - and not a germ we expected
    A wet El Niño turned the Four Corners lush and a hidden hantavirus began killing healthy young people - how did rain become a killer?

    The rain that fed twentyfold mouse booms - and not a germ we expected

    In this episode, we follow the documented chain that links an El Niño-driven wet spring to a sudden cluster of mysterious respiratory deaths in the Four Corners region. We trace each step from ocean temperatures to vegetation, rodent population booms, and the human exposures that followed - but what exactly tipped the balance into outbreak?

    Person: Deer mouse (Peromyscus maniculatus)
    Location: Four Corners region (Utah, Colorado, Arizona, New Mexico)
    Date: Spring 1993 (documented timeline begins ~one year earlier)
    Event: El Niño-driven heavy precipitation leading to vegetation bloom
    Topic: Hantavirus Pulmonary Syndrome transmission via dried rodent excreta

    - An El Niño cycle brought abnormally heavy rainfall to the normally semi-arid Southwest, starting roughly a year before the first deaths.
    - The desert bloomed: pinyon trees and other vegetation produced abundant seeds, transforming habitat and food availability.
    - Deer mouse populations rose dramatically-recorded data show approximately a twentyfold increase in the affected area.
    - The mice carried Hantavirus Pulmonary Nombre and shed virus in urine, feces, and saliva that dried into airborne dust when disturbed.
    - Human cases appeared months after the rain as people encountered contaminated dust in cabins, barns, and enclosed spaces, creating a delayed, geographically scattered outbreak.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    16 min
  • The Wat Romlok inscription reset Longvek's fall to 1594 - not 1583
    A Khmer capital on the Tonle Sap falls on 3 January 1594 - a Wat Romlok inscription forces historians to ask: which mattered most?

    The Wat Romlok inscription reset Longvek's fall to 1594 - not 1583

    In this episode, we lay out the competing dates and conflicting chronicles around the fall of Longvek and explain the stone evidence at Wat Romlok. What do an eleven-year discrepancy and carved inscriptions reveal about motive, memory, and power?

    Person: King Ang Chan I
    Date: 3 January 1594
    Location: Longvek, banks of the Tonle Sap
    Event: Fall of the Khmer capital
    Source: Inscription K.27 at Wat Romlok

    - Archaeologists in 1994 confirmed the fall date carved as 3 January 1594 on inscription K.27 at Wat Romlok.
    - Siamese chronicles consistently record the conflict beginning in 1583 and present the invasion as a defensive response to Khmer aggression.
    - Khmer chronicles claim Khmer forces had aided Siam against Burma and were betrayed during withdrawal, not the aggressors.
    - Longvek was founded c.1516 as a deliberate base for Khmer recovery, with river access, trade links, stone temples, and European mercenaries like Diogo Veloso.
    - By the final siege the court was divided: King Chey Chettha I (Satha) had ritual ties to Angkor and had positioned young sons for succession, while senior official Uparaja Sri Suriyobarm was reportedly frustrated with the arrangement.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    18 min
  • The railway explosion that toppled Zhang Zuolin, not a Chinese plot
    A Kwantung Army bomb derails a private train outside Mukden, killing a warlord - how did a railway incident reshape Manchuria and power in East Asia?

    The railway explosion that toppled Zhang Zuolin, not a Chinese plot

    In this episode, we trace how railways, corporations, and a standing army were assembled into an imperial mechanism in Manchuria. The episode follows the decisions, incidents, and institutional practices that turned a commercial corridor into a tool of political control and asks how a single railway attack fit into that system.

    Person: Puyi
    Person: Zhang Zuolin
    Organization: Kwantung Army
    Event: Railway bombing outside Mukden, June 4, 1928
    Company: South Manchuria Railway Company

    - The South Manchuria Railway Company operated with a leased corridor and a Japanese garrison, blending commercial and sovereign authority.
    - Japan paired corporate franchises with military force across its empire, modeling an institutional method adapted from European precedents.
    - Tokyo supported Zhang Zuolin as a client ruler until the Kwantung Army placed a bomb under his train when he became inconvenient.
    - The Kwantung Army staged a later railway explosion near Mukden in 1931 and blamed Chinese saboteurs to justify invasion.
    - Within months of the 1931 incident Puyi was installed and later declared Emperor of Manchukuo, a state structured by dual public and operational narratives.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    17 min
  • The Gilani brothers' defection stopped Vijayanagara's advance and emptied Hampi
    A deserted Vijayanagara of intact houses; two mercenary brothers in command may explain why the massive army halted at noon?

    The Gilani brothers' defection stopped Vijayanagara's advance and emptied Hampi

    In this episode, we follow accounts from travelers, inscriptions, and modern historians to trace how a wealthy, engineered empire reached the battlefield of Talikota and then silent Hampi. We ask how decisions, technology, and two commanders shaped the turning point that emptied a capital.

    Person: Cesare Federici
    Person: Domingo Paes
    Person: Krishna Deva Raya
    Event: Battle of 1565 (Talikota)
    Topic: Gilani brothers' command and loyalty

    - Cesare Federici visited Hampi decades after 1565 and reported every house standing but empty, occupied only by tigers.
    - Domingo Paes described Vijayanagara at its height (c.1509-1529) as a city "as large as Rome" with vast markets and armies.
    - Krishna Deva Raya (r. c.1509-1529) led a decisive victory at Raichur in 1520 that influenced later military doctrine.
    - By 1565 Vijayanagara's forces relied on infantry tactics and legacy practices developed after Raichur, while Deccan sultanates increased artillery and cavalry capabilities.
    - Two mercenary commanders known as the Gilani brothers led large contingents inside Vijayanagara's army and their conditional loyalty correlated with the army's loss of cohesion at noon.

    To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

    © 2026 OBOMEDIA. All rights reserved.
    This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: [email protected].
    18 min

About Empires Before The Fall

From the publisher's feed

Sometimes a place feels older than its ruins. You stand where thousands once lived, ruled, celebrated, and vanished, and for a moment the silence feels occupied. Empires Before The Fall explores that…