Firecrawl had 12 outages in the last 2 years totaling 9h 18m of downtime — averaging 0.5 incidents per month.
There were 12 Firecrawl outages since October 5, 2025 totaling 9h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
Our /interact and /browser APIs are currently unavailable due to an outage at an upstream provider. We are monitoring the situation
The API has recovered.
We’re back! API and dashboard should be up and running. Thanks for bearing with us.
We are investigating
We are investigating
We're back! API and dashboard should be up and running. Thanks for bearing with us.
We are investigating.
Everything should be working now. We are still monitoring it.
Switching teams and creating new user accounts are failing. We are investigating. API is unaffected.
The issue is resolved.
We are investigating
The issue has been fully resolved.
We are investigating.
Services have been restored to full capacity. We are looking into the cause of the issue.
We are seeing intermittent failures of the queuing system powering Crawl and Batch Scrape. We are working on a resolution.
We have applied a fix and the issue should now be resolved. We are continuing to monitor the situation closely.
We're seeing an elevated error rate on the Search endpoint. We are investigating.
The issue is now resolved.
api.firecrawl.dev is degraded.
The API issues have been resolved. An update to our ingress had caused incorrect SSL certificates to be served, but the correct certificates have now been applied.
The API issues have been resolved. An update to our ingress had caused incorrect SSL certificates to be served, but the correct certificates have now been applied.
We are experiencing elevated database-related errors. We are investigating.
We are seeing complete system recovery. We will continue to monitor the system.
Timeouts are elevated. We are working on the issue.
The issue has been resolved.