The Conspiratory

The archive, day by day

On this day in conspiracies

The dated turning points behind the case files: assassinations, crashes, leaks, votes, and the moments a theory was born, each drawn straight from a file's sourced timeline. We only place an entry on a day the record actually names.

  1. 1817
    Gloucester sea serpentCryptids & Monsters

    According to later accounts, a strange serpent-like animal is seen entering the harbor at Cape Ann, north of Gloucester. Word spreads quickly through the fishing community and to Boston.

  2. 1930
    Judge Crater disappearanceUnsolved Crimes & Disappearances

    In his chambers that morning Crater spends about two hours going through files; court staff later say he destroyed papers. He has a law clerk, Joseph Mara, cash two checks totaling about $5,150, and at midday the two men carry two locked briefcases to Crater's apartment. He tells Mara to take the afternoon off.

  3. 1997
    Rajneeshee salmonella attackSecret Societies & Power

    After a twelve-year delay requested by investigators who feared inspiring copycats, a detailed epidemiological analysis by Thomas Torok and colleagues is published in JAMA, laying out how the outbreak was investigated and confirmed as intentional. No wave of copycat attacks had followed.

  4. 2008
    Anthrax attacksGovernment & Intelligence

    At a press conference, Justice Department and FBI officials name Ivins as the sole perpetrator, resting the case in large part on a flask of anthrax in his lab, designated RMR-1029, that they say was the genetic parent of the attack spores.

  5. 2024
    CrowdStrike outageScience, Space & Technology

    CrowdStrike releases its full External Technical Root Cause Analysis of Channel File 291. It explains that a template type defined 21 input parameter fields while the integration code supplied only 20 values; a later instance introduced a non-wildcard match on the 21st field, causing the Content Interpreter to perform an out-of-bounds memory read and crash. It states that a third-party review confirmed the bug was not exploitable by a threat actor.

Drawn from 1,911 dated events across our case-file timelines. Dates reckoned in UTC.