An inefficient method to remove an object with large number associated objects was being called subsequent times before it completed, causing other requests to queue. The method has been identified and a performance fix is put in place.
Posted Mar 08, 2019 - 18:24 UTC
Monitoring
We have restored service and are looking into the root cause.