Firecrawl logo

Is Firecrawl Down?

SaaSLive status, outages, and incident history

No. Firecrawl is up right now.

Every monitored Firecrawl system is operational as of November 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Firecrawl breaks

Firecrawl is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Firecrawl status page
How we know: the official Firecrawl status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Firecrawl Status Summary

As of 02:36 UTC on 11 November 2026, Firecrawl is operational. PulsAPI checked Firecrawl's official status page and found 2 of 2 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Firecrawl, counting degraded performance as up. The latest incident, "/scrape latency degraded", was on Sep 15, 2026 and lasted 46 min.

Cite as: PulsAPI, “Firecrawl status”, checked 11 November 2026, 02:36 UTC. https://www.pulsapi.com/services/firecrawl

Firecrawl Component Status

The main Firecrawl systems on this page. All 2 are operational right now.

2operational
api.firecrawl.dev
Operational
firecrawl.dev
Operational

Component statuses may change independently during partial outages.

Recent Firecrawl Outages & Incidents

Incident history from the official Firecrawl status page, including resolution updates.

/scrape latency degradedResolved Sep 15, 2026 · 46 minResolved
/scrape is degradedResolved Sep 6, 2026 · 7 minResolved
API is degradedResolved Sep 3, 2026 · 16 minResolved

Firecrawl Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Firecrawl incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 13100.00% average · 3 days with incidentsNov 11

Going further back: Firecrawl uptime by month and every recorded Firecrawl outage.

Live Firecrawl Outage Reports

Problems reported by engineers using Firecrawl. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Firecrawl problems reported yet.

Something wrong with Firecrawl on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Firecrawl

Firecrawl maintains a public status page at status.firecrawl.dev reporting overall service health. Follow Firecrawl downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Firecrawl uptime at 100.00%. Response times, incident history, and SLA tracking for Firecrawl are available on the PulsAPI dashboard.

Firecrawl Status FAQ

Is Firecrawl down right now?

The verdict at the top of this page comes from the latest poll of the official Firecrawl status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Firecrawl is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Firecrawl recovers.

How do I check Firecrawl uptime history?

PulsAPI tracks Firecrawl uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Firecrawl changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Firecrawl outages?

PulsAPI reads the official Firecrawl status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Firecrawl components?

Yes. PulsAPI monitors 2 individual Firecrawl components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Firecrawl goes down?

Yes. Create a free account and subscribe to Firecrawl: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Firecrawl to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Firecrawl problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Firecrawl?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Firecrawl plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Firecrawl with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services