- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 100
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 23m it lasted.
Anything that failed between 2025-10-20 16:26 UTC and 2025-10-20 16:49 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 2
- update
We are experiencing elevated timeouts. We are investigating.
provider
- resolved
The issue is now resolved. As part of the hotfix, all ongoing concurrency queued jobs had to be discarded, causing ongoing crawls to freeze -- please reach out to support if you are affected. We apologize for the disturbance, and thank you for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-0cf32f9a2a
Is Firecrawl still down?
No, this incident was resolved 2025-10-20 16:49 UTC. For Firecrawl's live state, see https://down.guide/firecrawl.
How long did it last?
23m, from 2025-10-20 16:26 UTC to 2025-10-20 16:49 UTC, by the times Firecrawl posted.
What caused it?
Firecrawl hasn't published a root cause. If it does, it shows here.
Where does this come from?
Firecrawl's official status page, https://status.firecrawl.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.