
Apollo.io leads scraper
Pricing
$45.00/month + usage

Apollo.io leads scraper
Scrape leads from apollo io search results including verified emails and phone numbers. This apollo io data scraping bot helps you to extract leads from your apollo search results without subscribing to costly apollo pricing plans
1.7 (12)
Pricing
$45.00/month + usage
360
Total users
28K
Monthly users
1.2K
Runs succeeded
85%
Issues response
3.7 hours
Last modified
2 days ago
Run stopped with 0 contacts extracted - RequestError: Proxy responded with 590 UPSTREAM502: 0 bytes
Closed
I am curious as to why this error happened.
Just for context. I have been using the scraper for weeks with 3 different apollo accounts and residential proxies inside apify.
The scraper in this account was working fine before this error run and after 30 mins it worked fine as well (There are no issues anymore, just want to understand what happened to avoid the error in the future).
I scrapped 1 search url with this same account, it took longer than expected (3 mins for 37 results) because the search url had very few contacts in it.
Then I changed to another search url and scrapped 450 contacts there in 5 mins (this is expected behavior according to what I've seen so far).
Then, I tried scrapping another 450 with that same apollo search url and got that error.
Then I waited for 30 mins and scrapped that same search url and it worked fine again (extracted 450 contacts).
What went wrong in this run?
2024-02-22T10:28:46.756Z ACTOR: Pulling Docker image of build DetfulK5sVY88BpWG from repository. 2024-02-22T10:28:48.524Z ACTOR: Creating Docker container. 2024-02-22T10:28:49.135Z ACTOR: Starting Docker container. 2024-02-22T10:28:52.105Z INFO System info {"apifyVersion":"3.1.4","apifyClientVersion":"2.7.1","crawleeVersion":"3.3.2","osType":"Linux","nodeVersion":"v16.20.2"} 2024-02-22T10:29:07.035Z RequestError: Proxy responded with 590 UPSTREAM502: 0 bytes 2024-02-22T10:29:07.041Z at Request._beforeError (/usr/src/app/node_modules/got-cjs/dist/source/c... [trimmed]

This is a random error is related to proxy server and it goes off when we retry. I missed to add retry logic to one of the steps. Will fix it in next update

May be issue with proxy country. If possible try with different country and stick to it