For those of you who have been following The Curious Case of The Bandwidth Bandits, we finally have resolution, and it’s a good one. The system admins at my hosting company were able to solve the case, concluding I didn’t go .5 TB over my bandwidth limit for the month, and I won’t be on the hook for a $2000. hosting bill. Technical jibber jabber follows, but what’s important (besides not going broke over a blog, that’s very important) is that the tunes will be returning to I Rock Cleveland. I’m re-upping many of the links from the front page as I type this post. However, I won’t be re-upping any of the tunes by Bears, there’s some seriously bad juju on those mp3s.

The bandwidth calculation on the (ss) platform are done based upon the bytes requested as logged by apache. While this is standard practice, it does not take into account connections that are terminated before the download is complete. Typically the byte requested and bytes transfer are virtually identical. However, is some rare cases the can be drastically different. Looking at your raw web logs, I see thousands of lines like this:

217.68.80.146 – – [30/Aug/2008:04:10:59 -0700] “GET /tunes/SinceIMetYou.mp3 HTTP/1.1″ 200 4866685 “http://irockcleveland.blogspot.com/2008/08/rockometer-simple-machinery-by-bears.html” “Mozilla/4.0 (compatible; MSIE 5.00; Windows 98)”
217.68.80.146 – – [30/Aug/2008:04:10:59 -0700] “GET /tunes/SinceIMetYou.mp3 HTTP/1.1″ 200 4866685 “http://irockcleveland.blogspot.com/2008/08/rockometer-simple-machinery-by-bears.html” “Mozilla/4.0 (compatible; MSIE 5.00; Windows 98)”
217.68.80.146 – – [30/Aug/2008:04:11:00 -0700] “GET /tunes/SinceIMetYou.mp3 HTTP/1.1″ 200 4866685 “http://irockcleveland.blogspot.com/2008/08/rockometer-simple-machinery-by-bears.html” “Mozilla/4.0 (compatible; MSIE 5.00; Windows 98)”

This shows one IP repeatedly requesting /tunes/SinceIMetYou.mp3. While I am certain some of the data was actually delivered, the amount that was actually transfered is probably negligible.