- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 23of 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 7m it lasted.
Anything that failed between 2025-11-10 17:07 UTC and 2025-11-10 17:14 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
- update
We are experiencing elevated request failures. We have already identified the core issue and we are working on a swift resolution
provider
- update
The fix has been shipped. We are still degraded but we expect to be back at full availability in ~5 minutes.
provider
- resolved
The elevated API timeouts have been fully resolved. All services are operating normally. We apologize for the disruption and appreciate 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-9a602f5291
Is Firecrawl still down?
No, this incident was resolved 2025-11-10 17:14 UTC. For Firecrawl's live state, see https://down.guide/firecrawl.
How long did it last?
7m, from 2025-11-10 17:07 UTC to 2025-11-10 17:14 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.