Live / Incidents / Firecrawl
Firecrawl: /scrape latency degraded
Firecrawl · firecrawl.devImpact: minorResolved2026-09-15 14:50 UTC
Public — what happened
Summary
/scrape has recovered. We will continue to monitor and make improvements.
Timeline
- Started — 2026-09-15 14:04 UTC
- Last update — 2026-09-15 14:50 UTC
- Resolved — 2026-09-15 14:50 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Firecrawl against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Firecrawl: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Firecrawl report →