thanks for reporting. we made a change that should have resolved the 503s. can you confirm if working properly now? cc: @kol3x as you had the same issue