# Elevated timeouts

- Provider: [Firecrawl](https://down.guide/providers/firecrawl)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 2h 31m
- started 2025-10-29 21:17 UTC
- id: DWN-69f04a6ae4
- Official page: https://status.firecrawl.dev/incident/754103

## Root cause
> 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.

[Postmortem](https://status.firecrawl.dev/incident/754103)

## Updates from Firecrawl
### 2025-10-29 21:17 UTC: update
We are experiencing elevated timeouts. We are currently investigating.

### 2025-10-29 21:29 UTC: update
The issue is resolved. Thank you for your patience.

### 2025-10-29 23:48 UTC: resolved
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.

From the builder: does your app depend on Firecrawl? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=firecrawl) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Firecrawl.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-69f04a6ae4), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.