- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.firecrawl.dev
- Down Index
- 27of 100
What to do
Check whether you use Firecrawl api.firecrawl.dev. 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 46m it lasted.
Anything that failed between 2026-09-15 14:04 UTC and 2026-09-15 14:50 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
- degraded
We are seeing a latency degradation on /scrape. We are investigating
provider
- resolved
/scrape has recovered. We will continue to monitor and make improvements.
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-6eb16d3f53
Is Firecrawl still down?
No, this incident was resolved 2026-09-15 14:50 UTC. For Firecrawl's live state, see https://down.guide/firecrawl.
How long did it last?
46m, from 2026-09-15 14:04 UTC to 2026-09-15 14:50 UTC, by the times Firecrawl posted.
What was affected?
Firecrawl named api.firecrawl.dev.
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.