We had the same issue, but it seems to have been resolved now.