Sunday, July 10, 2011

We're investigating reports of 503 errors this morning, and hope to have the issue resolved shortly. We'll update this thread once we have more information to share.

Update, 2:00PST: This has been resolved, thanks for your patience.