Cloud. Turns out it was an issue with whether you landed on http://www.leaky.com or http://leaky.com. 302 Redirect has now fixed some of the errors.