Is Firecrawl down?
Right now
No. Firecrawl is operational.
No incidents reported.
Read from status.firecrawl.dev · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/firecrawl/status.agent.json
MCP: upstream_status {"service":"firecrawl"}
Web scraping and crawling API for LLM context.
What Firecrawl reports
Operational
Taken as is from Firecrawl's own status page API. Incident titles and component names below are theirs.
Open status.firecrawl.devUpButler's independent probe
There is no keyless endpoint of Firecrawl that says anything useful, so UpButler does not probe it. To check your own Firecrawl account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Firecrawl components
2 operational
Current status by service
- api.firecrawl.devOperational
- firecrawl.devOperational
Firecrawl incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Firecrawl publishes for 90 days from the day it starts tracking a service.
Tell your outage from Firecrawl's
Declare that your project depends on Firecrawl. When one of your monitors fails while Firecrawl has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- firecrawlcurl -s https://upbutler.com/status/firecrawl/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "firecrawl",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Firecrawl down right now?
- No. As of 2026-10-10 05:05 UTC, Firecrawl is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Firecrawl's own status page API at https://status.firecrawl.dev. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Firecrawl's words.
- How can my agent or app check Firecrawl status?
- Fetch https://upbutler.com/status/firecrawl/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"firecrawl"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Firecrawl's?
- Add "firecrawl" to the dependencies of your UpButler workspace. When one of your monitors fails while Firecrawl has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in search and web data
UpButler is not affiliated with Firecrawl. Status and incident text belong to Firecrawl and are read from their public status source; the probe result is UpButler's own measurement.