We have identified the problem and fixed the bottleneck on the tracker. It should no longer give any timeout/502 errors. If you are still getting these issues, please make sure to let us know!

--ATH

Discuss this post here