Podcasting has always been two things bolted together: an RSS feed that describes episodes, and a hosting account that stores the audio files the feed points to. The arrangement works invisibly until one half stops being paid for or gets switched off. Then the episodes in that account vanish the way a dead domain vanishes — except the show’s listings sometimes stick around, pointing at nothing.
In March 2024, true-crime host Kaigan Carrie’s show Evolving Prisons, hosted through Spotify for Podcasters, landed an Outstanding Indie Podcast nomination at the True Crime Awards. Less than 48 hours later her account was flagged for “suspicious payments activity” and, within five minutes, deleted. Because the RSS feed disappeared at the same time, Podnews reported that the show began to be dropped from other platforms, including Apple Podcasts. Spotify later restored the audio and, after Podnews followed up, reimbursed lost revenue and emailed former subscribers. What it could not restore was the audience. “I’ve lost every single person that was ‘following’ my podcast,” Carrie told Podnews — those followers, in every other app, were not coming back.
The feed is the show
Each item in a podcast feed carries a title, a description, a publish date, and an enclosure: a URL pointing at the audio file, which lives on the hosting service’s servers, not inside the feed. Directory apps like Apple Podcasts and Spotify mostly just fetch that feed and play what it points to.
The feed is therefore not the audio itself — it is the wiring that tells podcast apps what exists and where to fetch it. Break it and every app depending on it can fail at once. During a 2019 FeedPress outage, many podcast episodes became unreachable for hours because a shared RSS dependency went down. The outage was temporary; the dependency is structural.
What a dead account removes
When a hosting account dies, the damage is never just one file. A host bundles the audio, per-episode metadata, artwork, analytics, and feed. Simplecast’s help documentation warns that deleting a show permanently purges the podcast details, audio files, analytics, and RSS feed and recommends moving the feed and downloading files before deletion. Cancelled subscriptions, lapsed free accounts, and closed-down hosts take the whole bundle with them, leaving episode links to return nothing but 404s.
The cascade
That one deletion propagates. Downloads already queued in apps fail for months, old links across the web — in blog posts, archives, and show pages — all point at the same dead URL, and because nobody controls the expired account, nothing redirects anywhere. Episode listings may survive in the Wayback Machine or in a directory that polled the feed before it died, so the show can still look present while playing nothing.
What survives
Recovery starts with feed metadata. A captured RSS feed preserves the full episode index — titles, dates, descriptions, and the audio URLs — so the record of what existed and when is usually not the hard part. The hard part is the audio itself. It survives only where someone copied it: in a listener’s download folder, on a backup drive, or on archive.org, which hosts podcast episodes people upload deliberately. Tools that bulk-download podcast enclosures exist precisely because a feed can outlive the availability of the files it once listed.
That asymmetry is the useful lesson. Feed metadata rebuilds an index of what was lost, but an index is not an episode. The sound is gone unless someone, somewhere, pressed download.