The source of the issue was found to be with a specific Tomcat process. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent this from happening again.
Posted May 31, 2018 - 19:57 UTC
Monitoring
We found that the slowness/degraded performance is due to the heap memory usage on the affected instance. Currently the instance is back to normal and we are investigating the root cause of the issue that lead to the increase in heap memory usage. We will update this page once we have found the source of the issue.
Posted May 30, 2018 - 21:42 UTC
This incident affected: US - East1 (N. Virginia) - AWS (Artifactory).