It’s weekly update time!! As always, we’ve worked hard to listen to what you’d love to see in Captivate and have put together the latest release as follows…
- Brand new “system status” area – we’d planned this for Q4 2019 but accelerated its development in light of the StackPath challenge below. We now have a complete and comprehensive system status area for Captivate’s entire infrastructure. This has its own page right here at https://status.captivate.fm and system status will also show within the live chat support section at the bottom-right of Captivate’s dashboard. Whoop!
- Extra layer of object storage added – our CDN provider, StackPath, had an issue with its object storage node on the US East Coast. The object storage nodes are used to store your audio files before they get to the CDN when requested by a podcast player, plus they store other items such as podcast cover art – this issue with StackPath meant that uploads were sporadically failing and that audio sometimes couldn’t be quickly played back because the CDN couldn’t grab the audio file every time from the object storage system. StackPath is mega-reliable but just like any tech company, they do have some issues now and then – luckily, this is very very rare. We added an extra object storage redundancy layer which means that if StackPath ever has issues again, uploads will instantly switch to our secondary storage option seamlessly and automatically with no impact on upload or download speed. Bottom line: the issues that you may have experienced this week won’t happen again. Thanks for bearing with us 🙂
- Apple Podcasts URL format change in Captivate’s marketing section – in some instances, we were spotting that some Apple URLs weren’t validating correctly within the marketing section of your Captivate dashboard. As it happens… Apple has a couple of different URL formats so we added extra validation for them. Awww yeah.
All relevant help articles have been updated to reflect these changes.Listen to this episode