- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 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 4h 54m it lasted.
Anything that failed between 2026-10-28 05:55 UTC and 2026-10-28 10:49 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 3
- investigating
Our JS rendered scrapers currently have a degraded performance, and some customers may see significantly increased latency. Team is investigating.
provider
- identified
We have identified the root cause and are working on actions to mitigate the impact and bring service back to normal.
provider
- resolved
JS rendered jobs are back to normal.
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-ec18d1b6ab
Is ScrapingBee still down?
No, this incident was resolved 2026-10-28 10:49 UTC. For ScrapingBee's live state, see https://down.guide/scrapingbee.
How long did it last?
4h 54m, from 2026-10-28 05:55 UTC to 2026-10-28 10:49 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.