Firecrawl experienced a major incident on October 29, 2025 affecting Current status by service (api.firecrawl.dev), lasting 2h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 09:17 PM UTC
We are experiencing elevated timeouts. We are currently investigating.
- investigating Oct 29, 2025, 11:48 PM UTC
Customers who were exceeding their concurrency limit during this outage may be encountering strange errors in their crawls. This is due to the nature of the outage affecting our concurrency limiting system, causing unique jobs to be inserted into a separate per-team concurrency queue multiple times. When these jobs are promoted from the concurrency queue into the main queue, they retain their IDs, which causes a violation of the unique ID constraint. A fix for this issue is now deployed.