outages.live
Live
FirecrawlIncident ·

/scrape latency degraded

ResolvedOfficial update

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

The latest update from Firecrawl.

State

Resolved

Started

Lasted

46 min

Worst impact

Degraded

Timeline

2 updates
14:0414:1514:2714:3814:50
DegradedUpdate postedTimes in UTC

Degraded

46 min 100%

Updates

Times in UTC

As posted by Firecrawl

Resolved

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

Degraded

We are seeing a latency degradation on /scrape. We are investigating

Affected components

1
api.firecrawl.dev

Firecrawl in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

16 min

This incident

2.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

46 min
median 16 min
90 days agoToday

Other Firecrawl incidents

All incidents

Firecrawl·/scrape is degraded

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

Resolved

Firecrawl·API is degraded

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.

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane