Elevated latency on Crawling API

Between 06:40 and 07:25 UTC a subset of requests to the Crawling API experienced higher than normal response times, with some requests timing out and being retried. The cause was a saturated queue in one of our request routing clusters after a spike in traffic. Capacity has been increased and traffic redistributed across the remaining clusters. All requests are now being served at normal speed.