There aren't a lot of people who can say they were a showrunner on a series that got canceled and later saw the cancellation get reversed by another network. The Expanse showrunner Naren Shankar is one of those lucky few people, and this year during an Amazon Showcase at Comic-Con 2018, Shankar shared the incredible story of how he learned The Expanse was being picked up at Amazon, and Amazon's Jeff Bezos has his hand in the surprise. As Shankar tells it, he didn't get a call when the show was renewed. Instead,
The Expanse isn't the first time a viral movement led to a show being brought back from the day. Even Longmire saw its day in the sun. However, it's still rare for a show to come back from the dead and The Expanse experience was a little different than many of the stories we've heard about projects getting saved from cancelation. The fandom found creative and unique ways to express their love for the show after its cancellation, and Naren Shankar also talked at Comic-Con about how amazing it was to be along for the ride.
The experiences Naren Shankar mentions have been well-documented online, and if you haven't looked into it, they are even fun for non-fans. The fanbase really made stuff happen for the show and was so much gratitude when The Expanse was picked up by Amazon for a fourth season, and moving to streaming means that there are fewer restrictions on the show to fit into cable television standards. Expect some changes, including fewer language restrictions and new length times, but the cast is coming back and we can expect it to still be the show we know and love.
The Expanse is expected to return to Amazon in 2019, and we'll keep you updated with more details as we have them. In the meantime, stay tuned for more Comic-Con 2018 coverage.
Amazing Race & Top Chef superfan with a pinch of Disney fairy dust thrown in. If you’ve created a rom-com I’ve probably watched it.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.