Firecrawl Outage History

9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Firecrawl Incident

Firecrawl incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 15, 2026/scrape latency degraded1216h 49mResolved
Sep 6, 2026/scrape is degraded1445h 8mResolved
Sep 3, 2026API is degraded1511h 41mResolved
Aug 27, 2026/interact API `prompt` field functionality is degraded1577h 56mResolved
Jul 20, 2026Interact endpoint is degraded1744h 34mResolved
Jun 19, 2026PDF scraping is degraded1773h 48mResolved
Jun 18, 2026Screenshots are degraded1781h 53mResolved
Jun 18, 2026API is degraded1783h 55mResolved
Jun 15, 2026/interact API unavailable1856h 54mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Firecrawl incident opens instead, at the point where knowing still changes what you do.

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

How to Read This Firecrawl Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Firecrawl acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Firecrawl outage in this window ran 77d 8h, against a mean recovery of 68d. If you depend on Firecrawl in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.