- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 39of 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 2025-10-02 15:15 UTC and 2025-10-02 15:59 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 working on resolving the isse.
provider
- resolved
The issue is now resolved. We apologize for the inconvenience. The maintenance we had previously scheduled for Sunday will address the root cause of this downtime.
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-2a5ff3309a
Is Firecrawl still down?
No, this incident was resolved 2025-10-02 15:59 UTC. For Firecrawl's live state, see https://down.guide/firecrawl.
How long did it last?
44m, from 2025-10-02 15:15 UTC to 2025-10-02 15:59 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.