Skip to main content
The website at the requested URL is returning an error page of its own (for example an HTTP 500 “Server error”, “Service Unavailable” or a hosting provider’s error screen). Supadata tried every scraping method it has and each one came back with that error page, so there is no page content to return. This is the target site’s outage, not a Supadata failure.
Returned by GET /v1/web/scrape with HTTP status 502. Requests that end in this error are not billed.

​
Reasons and how to fix

​
The page is broken on the website itself

Open the URL in a private/incognito browser window. If you see an error page there too, the site is down or the page is broken for everyone, and there is nothing to scrape until the site owner fixes it. To fix this:
  1. Retry later; sites often recover within minutes or hours
  2. Check whether a different URL for the same content works (for example the canonical product or article URL instead of a deep link)
  3. Avoid tight retry loops: each attempt runs the full scraping chain and will keep returning upstream-error until the site recovers

​
The site serves an error page only to automated requests

Some sites answer bots with an error page while browsers see the content. If the page works in your browser, reach out to support with the URL so we can look at the site’s behaviour.
A page that reports “not found” or “removed” returns not-found (404); a login wall or an anti-bot challenge returns forbidden (403). upstream-error is specifically for the site’s own server-error pages.

​
Reach out to support

If you continue to face issues or need further assistance, please reach out to support@supadata.ai, and we will assist you as soon as possible.