Apologies for the inconvenience, we're still trying to figure out the source of the issue and it appears we were mistaken. Please bare with us a little longer.