Live

API requests timing out

0

Between 09:55 and 10:33 UTC on Nov 19, many API requests (scrape, search, crawl and interact) timed out or returned 502 errors, in three windows: 09:55-10:03, 10:05-10:14 and 10:22-10:32. One of our internal Redis instances became overloaded and stopped responding, and API requests waited on it. We restarted it at 10:32, and the API has been healthy since. We're shipping fixes so a stall like this fails fast and the load pattern that caused it can't recur.

The latest update from Firecrawl.

State

Resolved

Started

Lasted

2 h 17 min

Worst impact

Degraded

Timeline

1 update
09:5510:2911:0311:3712:11
NoticeUpdate postedTimes in UTC

Resolved

2 h 17 min 100%

Updates

Times in UTC

As posted by Firecrawl

Resolved

Between 09:55 and 10:33 UTC on Nov 19, many API requests (scrape, search, crawl and interact) timed out or returned 502 errors, in three windows: 09:55-10:03, 10:05-10:14 and 10:22-10:32. One of our internal Redis instances became overloaded and stopped responding, and API requests waited on it. We restarted it at 10:32, and the API has been healthy since. We're shipping fixes so a stall like this fails fast and the load pattern that caused it can't recur.

Affected components

1
api.firecrawl.dev

Firecrawl in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

31 min

This incident

4.4× the median

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

2 h 17 min
median 31 min
90 days agoToday

Other Firecrawl incidents

All incidents

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