Previous incidents

The API was unavailable for about 2 minutes due to an internal networking error that affected the connection to our Redis instance. This issue is now resolved.

All services are back online. Still monitoring it for issues.

An additional fix has been applied to prevent this failure case from happening again. Crawls and batch scrapes submitted in the past 24 hours are unavailable via the API, but downloadable through the Dashboard. In-progress crawl, batch scrape, and extract jobs were interrupted.

The issue has been resolved. Due to a step in our resolution, crawls and batch scrapes from the past 24 hours are not accessible via the API, they are only downloadable through the dashboard.

The issue is now resolved.

We've pushed numerous fixes to make sure this issue stays resolved.

We are back. Access to crawls made in the past 24 hours may be impacted, please contact support if you need a large crawl retrieved with a crawl ID. Crawls running at the time of incident had to be terminated. We apologize again for the disruption.

The service is now back up. Unfortunately, crawls made in the last 24 hours are no longer accessible through the API, and running crawls had to be interrupted due to the nature of the fix. Please contact support if you need help with an interrupted crawl.

We are back. Access to crawls made in the past 24 hours may be impacted, please contact support if you need a large crawl retrieved with a crawl ID. Crawls running at the time of incident had to be terminated. We apologise for the disruption.