Thanks for the heads up--it looks like we have an infrequent but recurring bug that's causing this issue. We're working on a more permanent fix for the very near future, but for now it should all be working again.