Elevated timeouts

What to do

• Check whether your product depends on Firecrawl. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 31m it lasted.

  Anything that failed between 2025-10-29 21:17 UTC and 2025-10-29 23:48 UTC may need a replay.

• Subscribe to Firecrawl's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=firecrawl works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Firecrawl 3

1. updateOct 29, 2025, 9:17 PM UTC

   We are experiencing elevated timeouts. We are currently investigating.

   provider

2. updateOct 29, 2025, 9:29 PM UTC

   The issue is resolved. Thank you for your patience.

   provider

3. resolvedOct 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.