A fix was rolled out for this issue, and the Async scraper is back up and running.
We now know where the issues lies and are working on fixing it.
Our Async scraper is currently down. We are aware of the fact that sending requests to our Async will result in 503 errors most of the times, and are already working on resolving this issue.