- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on ScrapingBee. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 15m it lasted.
Anything that failed between 2026-11-05 06:31 UTC and 2026-11-05 08:45 UTC may need a replay.Subscribe to ScrapingBee's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=scrapingbee works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from ScrapingBee 4
- identified
Our HTML scrapers (both js and non-js) have degraded performance, with increased level of errors and higher latency. We have identified the root cause, and are looking for a proper solution.
provider
- identified
Non-js scraper has recovered, while rendered one still is degraded. We are working to bring it back to normal.
provider
- monitoring
Both non-js and js scrapers are now back to normal. We are still closely monitoring the situation.
provider
- resolved
Incident is now resolved, we are fully operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f561b72754
Is ScrapingBee still down?
No, this incident was resolved 2026-11-05 08:45 UTC. For ScrapingBee's live state, see https://down.guide/scrapingbee.
How long did it last?
2h 15m, from 2026-11-05 06:31 UTC to 2026-11-05 08:45 UTC, by the times ScrapingBee posted.
What caused it?
ScrapingBee hasn't published a root cause. If it does, it shows here.
Where does this come from?
ScrapingBee's official status page, https://status.scrapingbee.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.