pingoru pingoru ScrapingBee had 38 outages in the last 2 years totaling 1901h 2m of downtime, averaging 1.6 incidents per month.
There were 38 ScrapingBee outages since November 7, 2024 totaling 1901h 2m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We have identified the cause of the degraded performance affecting our dedicated Google API and are working to resolve the issue. Customers may continue to experience a lower success rate on this endpoint while we implement a fix.
This incident has been resolved.
We have a degraded performance of both non-JS and render-JS requests, with success rates significantly below usual ones. Team is looking into it.
Issues resolved, scrapers back to normal performance.
Our Google, Amazon, ChatGPT, Gemini, Walmart and Youtube API's are currently returing errors for all the incoming requests. Fast Search is working as expected. Team is on it.
We are working on a temporary solution for the weekend to bring the service up. ETA within next 30 minutes.
We are back.
We are seeing depreciated success rate for non-JS requests. Our team has identified the cause and is applying an interim mitigation right now.
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.
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.
We are seeing depreciated success rate using our classic proxies with both JS and non-JS requests. Our team is aware of the issue and is looking to resolve it as soon as possible.
Our team was successfully able to identify the issue and resolve it.
Our ScrapingBee dashboard might be loading incorrectly currently, without styles being loaded. Team is looking into it.
We have identified that only users behind Fortinet global firewall are being affected. We are now geting in touch with Fortinet to resolve this as quicky as possible.
Issue resolved.
We have degraded performance on Fast Search API, with most of the requests failing. Team is looking into it.
Performance restored. We are monitoring.
Service is fully operational.
ScrapingBee API is down. Team is on it with highest priority
Service is fully restored.
We have a full outage of our HTML api as well as dedicated APIs. Team is on it with highest priority.
The core issue has been identified and fixed, services are restoring. We are monitoring the situation.
All services are now fully operational.
Our Google and Fast Search APIs are currently down. Team is investigating.
Both APIs are back to normal.
We have a degraded performance on Google API with requests failing and timing out. Team is investigating.
We have resolved the issue, Google API performance is back to normal.
We are noticing an increased timeout rate with our Walmart API. Our team is aware and investigating the issue.
Our team has identified the issue and resolved the incident!
We have highly increased amounts of false positives on ChatGPT API. Team is investigating.
Issue with false positives resolved.
Currently our Proxy Mode (https://www.scrapingbee.com/documentation/proxy-mode/) not working. Team is investigating.
Proxy Mode is back to normal.
We are observing increased false positives on Google API (200 status codes with empty responses). Small amount of requests affected so far, but the team is investigating and working to resolve the issue.
Issue resolved.
We are experiencing degraded performance on our Google and Walmart API, with much lower success rates and increased response times. Team is working to restore the services.
Service is restored.
We currently have increased error rates for POST requests. This is related to our migration to the new infrastructure. Team is looking into it with priority. Sorry for any inconvenience caused.
Issues has been fixed, success rates for POST requests are back to normal.
We are having issues with Google scraping since around midnight today, users mostly getting 500 errors. Our team will search for the best strategy how to mitigate that first thing in the morning. No ETA at the moment.
Google scraping is restored, though success rates and response times may still fluctuate a bit.
It is currently not possible to log into the dashboard via Google sign-in method. Team is working to resolve the issue.
Dashboard is now fully operational.
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.
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.
We are experiencing degraded performance on Google API. Our team is searching for the best strategy how to mitigate that. While we are actively testing different approaches, you may experience timeframes with elevated response time and decreased success rate. We apologize for the inconsistent performance during this time as we look for the best solution. No ETA at the moment.
Service restored and fully operational.
ScrapingBee API is currently having total outage. Team is working on it with priority.
Service restored and is fully operational.
Our ChatGPT API is having increased response times. Team is working on finding best strategies to resolve this. Currently no ETA.
Response times for ChatGPT have normalized.
Due to technical issues ScrapingBee dashboard is currently not accessible. Team is working to restore it.
Dashboard is up and running.
All services fully operational.
We are experiencing degraded performance on the Google API. Currently, the Google API does not return organic results. Our team is searching for the best strategy to mitigate that. We apologize for the inconvenience caused during this time as we work to find the best solution. No ETA at the moment.
Google API is returning results the same as before; the issue has been resolved