Artwork
iconShare
 
Manage episode 515887205 series 3654641
Content provided by Tyler Woodward. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tyler Woodward or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://staging.podcastplayer.com/legal.

The October 2025 AWS outage that took down major internet services for hours proves why broadcasters need multi-cloud redundancy and hybrid infrastructure to protect both revenue and emergency alerting capabilities. When automation goes down, commercials don't air, programming stops, listeners tune out, and advertising revenue disappears. Tyler breaks down why radio stations need backup systems using an analogy everyone understands: redundant internet connections.

Just like businesses maintain Spectrum as primary internet with Lumen as backup, broadcasters should run primary automation on AWS with backup on Azure or Google Cloud. When one cloud provider experiences DNS failures and outages, backup systems on different providers automatically take over, keeping programming running and revenue flowing.

This opinion episode covers why IP-based studio-to-transmitter links over single internet connections create vulnerability, why stations need backup STL paths through different providers or microwave links, and why broadcast automation distributed across multiple cloud providers prevents total station failure during provider outages. Tyler also discusses why on-premise EAS hardware should remain the foundation for emergency alerting even as CAP and IPAWS expand internet-based capabilities.

Dave's Garage technical analysis reveals why backup systems that depend on failed infrastructure don't actually work, and why true redundancy requires genuine independence between providers, just like backup internet connections use different backbone infrastructure.

Topics covered: AWS outage impact on broadcasting, multi-cloud redundancy for radio automation, hybrid on-premise and cloud infrastructure, IP STL backup strategies, EAS reliability considerations, broadcast revenue protection during cloud failures, redundant internet connection analogy for multi-cloud architecture, automation system failover, protecting morning drive advertising revenue, and why radio infrastructure diversity matters.

Send me a text message with your thoughts, questions, or feedback

Buzzsprout - Podcast Hosting
Podcast hosting made simple. Sign up and we both get $20 credit when you upgrade to paid plans.

Support the show

If you enjoyed the show, be sure to follow Fully Modulated and leave a rating and review on Apple Podcasts or your favorite podcast app—it really helps more people discover the show.

Fully Modulated is not affiliated with or endorsed by any station, media company, or network. All opinions are solely my own.

  continue reading

32 episodes