@loner614: Alright, we'll take a look at this again. Thanks for the extra info, guys.

@GameboyTroy: We're working on it. The fix happened to break something else, so we're just getting things sorted out. We're shooting for a fix today, or Monday at the latest.

@Cloud_imperium: It's working again - thanks!

@drrollinstein: Should work now, thanks!

@Seerix: Indeed, verified. We'll get it fixed.

@Hvac0120: We are definitely working on this consistently. The issue is that it's not just one "advertising software" that can fix it - every ad network these days is a network of networks, so the advertisers may be several steps away from the network we work with directly, so stomping out the clowns running these malicious ads is not a trivial task. That said, we battle on! The more info y'all can provide, the easier it is for us to clean it up. Thanks!

@br0kenrabbit: Huh, you're right. Will fix.

@life359: There are a variety of reasons this is challenging, but one of the biggest for us is that when you deal with the volume of bandwidth that we do (particularly for video), there is a significant difference in serving costs via CDN for https vs http. We have been working on re-negotiating our contract, and do hope to go to https in the future, but currently it's cost-prohibitive.

@Bamda: Good catch, looks like a mistake - I sent it over to our experts to verify/fix.

@Zassimick: Thanks for the info - we're on it!