Previous incidents

The issue is now resolved. As part of the hotfix, all ongoing concurrency queued jobs had to be discarded, causing ongoing crawls to freeze -- please reach out to support if you are affected. We apologize for the disturbance, and thank you for your patience.

The issue has been resolved. Thank you for your patience.

We've shipped a fix and the incident is now resolved. Thank you for your patience.

The elevated API timeouts have been fully resolved. All services are operating normally. We apologize for the disruption and appreciate your patience.

We have identified and pushed a hotfix for the root cause. We are working on a permanent fix.

The issue is now resolved. We apologize for the inconvenience. The maintenance we had previously scheduled for Sunday will address the root cause of this downtime.

Resolved

The incident has been resolved.

The issue is resolved. We switched the main Firecrawl service to our new queue system last week, however, Fire-Engine remained on the previous queue system, and experienced a failure similar to what Firecrawl was experiencing before the switch. We are working on switching Fire-Engine over to the new system as well.

We are back!

The issue was resolved.