QandO at the Crossroads
We’ve been having a big problem at QandO. The podcast, apparently, has gotten popular. Under our old hosting plan, we had 400GB of bandwidth. Last month, our bandwidth began to skyrocket, almost entirely due to podcast downloads. That has continued this month, too. The excess bandwidth charges for exceeding the monthly bandwidth allowance are $4 per GB.
Essentially, we’ve gone from an average of about 8GB in bandwidth per day to 50GB per day.
This is complicated by the fact that the old version of QandO was created way back in 2004 using ASP.NET 1.1. It works great. Sadly, it’s no longer supported by Microsoft. Last month, when it became clear we were going to blow through our bandwidth allowance, I did two things:
First, I removed the Stitcher podcast player from all the Podcasting posts, to avoid drive-by downloads from the post page. Second, I worked with the web host and was able to upgrade to the last existing ASP.Net 1.1 Premier plan, with a 600GB bandwidth limit, to avoid the bandwidth charges. That costs me $37/mo. As it turned out, bandwidth for the last week of July fell back to normal, so we only went through 415GB, which would’ve been a $60 excess bandwidth charge for the month.
So, increasing the bandwidth limit to 600GB should be a fix, right? Well, this month, we have already burned through 275.15GB in 10 days. At this rate, we will blow through the monthly bandwidth limit around Aug 22.
So, if you are looking for a podcast that’s more than a week old, you won’t find it. I’ve deleted all the older ones. Obviously, that isn’t an optimal solution.
The real solution is to move QandO over to a modern Cloud Hosting environment, which has unlimited bandwidth, 10GB of file storage, and only costs $18 per month. But, the newer hosting plans do not support ASP.NET 1.1. Essentially, that means that everything we’ve written prior to 2009 would, for a while, at least, disappear. I have the old legacy content in a big, honkin’ file, but it would take some time to restore the old content to a static HTML page. Ultimately, transferring that would be a lot of work.
In any event, while I’m happy the podcast is becoming more popular, it’s causing some problems with trying to reconcile a large chunk of legacy content with modern hosting solutions.
This is complicated by the fact that Jon Henke still owns the domain, so any changes to the server would require him to make the change at GoDaddy. Depending on how long that would take, moving to a new host could mean that QandO will go down for some period of time.
So,all of this is information for you to understand why the Podcast has no archives, and warning that QandO may have to go dark for a day or so if we change to a new hosting plan.