ScrapingBee incident

Degraded performance of our core HTML scrapers

Minor Resolved View vendor source →

ScrapingBee experienced a minor incident on February 10, 2026 affecting HTML Scraping and HTML Scraping with Rendering, lasting 38m. The incident has been resolved; the full update timeline is below.

Started
Feb 10, 2026, 06:47 PM UTC
Resolved
Feb 10, 2026, 07:26 PM UTC
Duration
38m
Detected by Pingoru
Feb 10, 2026, 06:47 PM UTC

Affected components

HTML ScrapingHTML Scraping with Rendering

Update timeline

  1. investigating Feb 10, 2026, 06:46 PM UTC

    We are observing degraded performance of our core HTML scrapers, users may experience significantly increased response times. Team is working to identify the root cause and restore the service.

  2. resolved Feb 10, 2026, 07:26 PM UTC

    We have identified the root cause, the problem was in HAProxy config. We still need to understand why it caused this degradation. But for now service is restored and fully operation, response times are back to normal.