outages.live
Live

Firecrawl

Firecrawl is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Firecrawl status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Firecrawl since . The days before that show only what Firecrawl published.

Incidents in 90 days

3

Days with an incident

3

Median duration

16 min

Longest incident

46 min

Components

2

Current status by service

api.firecrawl.dev Operational
90 days ago3 days with an incidentToday
firecrawl.dev Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 15, 2026

Duration46 min to /scrape latency degradedDegraded

/scrape has recovered. We will continue to monitor and make improvements.

Sep 6, 2026

Duration7 min to /scrape is degradedDegraded

The incident has been resolved. Apologies for the inconvenience. We will continue to monitor.

Sep 3, 2026

Duration16 min to API is degradedDegraded

Between 07:12 and 07:28 UTC today, a network issue in our upstream ISP caused a portion of jobs to fail. The issue resolved at 07:28 UTC and we are working on additional redundancy to avoid similar issues in the future.

Follow Firecrawl

Your coding agent knows when Firecrawl is down, and tells you when a failure is theirs, not yours. You can also get Firecrawl incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "firecrawl" and tell me if Firecrawl has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=firecrawl
Slack
/feed subscribe https://outages.live/feed.xml?providers=firecrawl

Go from tracking outages to fixing production issues with Polylane.

Try Polylane