Resolved after 11 hours 36 minutes, on June 3, 2026.
We have removed our proxy rerouting mitigation, restoring our original proxy setup. Outage issues with two of our upstream proxy suppliers have been resolved. We will continue monitoring error rates and investigating original root cause with our proxy suppliers. Before our team deployed mitigating rerouting solution, we had experienced scraping outage with ISP proxies.
Update timeline
- investigating Jun 03, 2026, 07:17 PM UTC
We are seeing depreciated success rate for non-JS requests. Our team has identified the cause and is applying an interim mitigation right now.
- monitoring Jun 03, 2026, 08:56 PM UTC
Our team has successfully deployed an interim solution to mitigate our proxy provider issues and restore non-JS success rates to baseline. We will continue monitoring the situation.
- resolved Jun 04, 2026, 06:57 AM UTC
We have removed our proxy rerouting mitigation, restoring our original proxy setup. Outage issues with two of our upstream proxy suppliers have been resolved. We will continue monitoring error rates and investigating original root cause with our proxy suppliers. Before our team deployed mitigating rerouting solution, we had experienced scraping outage with ISP proxies.
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.
Amazon Web Services