ScrapingBee incident

HTML scraper (js and non-js) performance degradation

Resolved after 2 hours 1 minute, affecting Core (HTML Scraping) and Core (HTML Scraping with Rendering), on November 5, 2026.

monitoring Nov 05, 2026, 08:32 AM UTC

Both non-js and js scrapers are now back to normal. We are still closely monitoring the situation.

Started
Nov 05, 2026, 06:31 AM UTC
Resolved
Nov 05, 2026, 08:32 AM UTC
Duration
2h 1m
Detected by Pingoru
Nov 05, 2026, 06:31 AM UTC

Affected components

Core (HTML Scraping)Core (HTML Scraping with Rendering)

Update timeline

  1. identified Nov 05, 2026, 06:31 AM UTC

    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.

  2. identified Nov 05, 2026, 07:49 AM UTC

    Non-js scraper has recovered, while rendered one still is degraded. We are working to bring it back to normal.

  3. monitoring Nov 05, 2026, 08:32 AM UTC

    Both non-js and js scrapers are now back to normal. We are still closely monitoring the situation.

  4. resolved Nov 05, 2026, 08:45 AM UTC

    Incident is now resolved, we are fully operational.

Your product runs on more than ScrapingBee

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →