Resolved -
This incident has been resolved. The underlying cause was determined to be a few lines of code which each had a few too many spaces, which ended up causing an obscure issue that was very difficult to pinpoint. We are working to put measures in place to change our testing procedures to avoid such an event from happening again. More information will follow in a Postmortem within the next few days.
Jun 24, 00:46 UTC
Update -
A fix is now being pushed to live servers.
Jun 23, 22:44 UTC
Identified -
We apologize for the large delay resolving this issue. A fix is being implemented and is currently being tested before being pushed to our live servers. We'll update with further information as soon as possible.
Jun 23, 21:38 UTC
Investigating -
We are currently investigating this issue.
Jun 23, 14:24 UTC
Identified -
Some users may experience delays. The issue has been identified and a fix is being implemented.
We are very sorry for the inconvenience this causes.
Jun 23, 12:40 UTC