Rewindex

CompaniesaiFirecrawl

Firecrawl

firecrawl.dev (opens in new tab)Status page (opens in new tab)

Status page says
Operational since Oct 19
Last 90 days
4 incidents
Rewrites caught
None so far
Next deprecation
None announced
Firecrawl incidents per day, last 90 days

Our copy of Firecrawl’s status page starts Aug 27; hatched days are before that. Select a day to jump to its incidents.

How Firecrawl reports incidents

Not enough incidents to compare Firecrawl with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Firecrawl has 4 and 4).

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

Dependencies

What Firecrawl relies on and who relies on Firecrawl, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Who depends on Firecrawl

VendorEvidenceSignal
Zapierlisted as a subprocessorWeak

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Changes and edits

Incidents Firecrawl rewrote or removed, and notable changes to the pages we watch.

Struck in red is what Firecrawl removed. Blue is what they added.

Full Firecrawl change history

Pricing and pages we watch

No pricing, trust or legal pages tracked for Firecrawl.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

The Weekly Rewind: one short weekly email on what changed at Firecrawl and the other vendors we track, including silent edits. Subscribe (opens in new tab)

Incidents

4 incidents since Aug 27. Maintenance is left out.

Tuesday, September 15

1 incident

Sunday, September 6

1 incident

Thursday, September 3

1 incident

Thursday, August 27

1 incident

Firecrawl incidents, last 90 daysJSONMarkdown