Scrapium
Affected: Cloud Browser
Scrapfly Outage History
Scrapfly is up right nowScrapfly had 9 outages in the last 2 years totaling 95h 3m of downtime, averaging 0.4 incidents per month.
There were 9 Scrapfly outages since December 27, 2024 totaling 95h 3m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Web Scraping API High Error Rate
Affected: Scraper
Timeline · 4 updates
- investigating Mar 18, 2026, 02:16 PM UTC
Since 12 AM, the API Error rate has increased and we are currently investigating the issue
- monitoring Mar 18, 2026, 02:36 PM UTC
A bug in our scraping infrastructure caused some requests to hang indefinitely when a specific configuration/target website was used, gradually consuming all available resources and leading to degraded performance. The issue has been identified and fixed.
- monitoring Mar 18, 2026, 02:37 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 19, 2026, 01:42 AM UTC
This incident has been resolved.
Browser allocation issue
Affected: Browser Pool
Timeline · 3 updates
- identified Feb 27, 2026, 04:24 PM UTC
The allocator to distribute traffic across our browser fleet is working in degraded until we reconfigure/resize correctly for the given traffic the instance group. Will be back in short minutes
- monitoring Feb 27, 2026, 04:25 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 27, 2026, 04:29 PM UTC
This incident has been resolved.
[ASP] Cloudflare is down and all target website protected by them are unreachable 🙃
Affected: Scraper
Timeline · 2 updates
- monitoring Nov 18, 2025, 01:58 PM UTC
It's not related to our end or the bypass, but due to a Cloudflare issue, we can't scrape those websites at the moment. See https://www.cloudflarestatus.com/ There is no need to contact our support regarding Cloudflare targets; it will work once Cloudflare is live again.
- resolved Nov 18, 2025, 03:01 PM UTC
This incident has been resolved.
Browser Pool Issue
Timeline · 1 update
- resolved Jun 26, 2025, 08:12 AM UTC
Auto scaling issue resulting in "no browser available"
Database issue
Affected: WebsiteScraperExtraction APIWeb Scraping APICloud BrowserSchedulerScreenshot APICrawler APIFingerprint API
Timeline · 4 updates
- investigating Jun 25, 2025, 07:49 AM UTC
It's been 2 days in a row that our master database has crashed with corruption during the early morning - we are working to bring the service back and investigate the problem further
- investigating Jun 25, 2025, 07:52 AM UTC
The master database availability is restored
- monitoring Jun 25, 2025, 07:55 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 25, 2025, 11:23 AM UTC
This incident has been resolved.
High demand on browser rendering
Affected: ScraperBrowser Pool
Timeline · 2 updates
- monitoring Apr 11, 2025, 12:38 PM UTC
We are currently receiving more than 1k req/s requesting browser rendering - We are scaling the infrastructure but the experience is degraded and might end in timeout on some scrapes
- resolved Apr 14, 2025, 12:59 PM UTC
This incident has been resolved.
Billing API Credit counted
Affected: Website
Timeline · 2 updates
- identified Jan 29, 2025, 11:26 AM UTC
Some customers have wrong API Credit reported. The issue is currently fixed. We are recomputing it against the scrape logs. If you have the wrong API credit reported, this will be updated during the day
- resolved Jan 29, 2025, 02:36 PM UTC
All impacted customers have been compensated and notified with the details of the operation on their quota
Sporadic Proxy Authentication Issue
Affected: Web Scraping API
Timeline · 4 updates
- investigating Dec 27, 2024, 12:09 PM UTC
Since yesterday at 3PM UTC, we have had an unhealthy proxy pool since we observed a sporadic 407 response across customers. We are working on it to resolve the issue
- monitoring Dec 27, 2024, 12:38 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 27, 2024, 01:32 PM UTC
This incident has been resolved.
- postmortem Dec 27, 2024, 01:33 PM UTC
We will implement a better fallback system, specially to detect such issue when multiple pools cascading into issue and balance across diffrent group to ensure their is no colocation with underlying unhealthy networks