- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 44m it lasted.
Anything that failed between 2026-07-20 07:20 UTC and 2026-07-20 08:04 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 investigating
provider
- resolved
The /interact and /browser APIs have fully recovered and are operating normally. The outage was caused by an issue at an upstream provider, which has since been resolved. All other Firecrawl APIs remained unaffected throughout the incident.
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-b67dfcc354
Is Firecrawl still down?
No, this incident was resolved 2026-07-20 08:04 UTC. For Firecrawl's live state, see https://down.guide/firecrawl.
How long did it last?
44m, from 2026-07-20 07:20 UTC to 2026-07-20 08:04 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.