Previous incidents

We're fully back up now.

Some crawls started between 9:30 PM EST and 10:30 PM EST may have been affected by the outage. If you need help, please reach out to help@firecrawl.com.

We sincerely apologize for the disruption in some requests. The issue was caused by a sudden surge in traffic (100x normal amount) that overwhelmed our internals and upstream providers. We're continuing to work with them to ensure this doesn't happen again.

A full incident report will be shared later this week.

The issue is resolved. We are investigating further.

We are fully back. We have also managed to upgrade our infrastructure during this time to avoid the errors experienced today in the future. Thank you for your patience.

The issue has been resolved for now and all services are fully operational. We're currently working with the GCP team as they continue investigating the root cause. Once their analysis is complete, we’ll publish a detailed incident report outlining what happened and the steps taken.
Thank you!

Issue is fixed. We are still monitoring closely.

We are back!

All /extract calls are working again.

The API has recovered.

The API was unavailable for about 2 minutes due to an internal networking error that affected the connection to our Redis instance. This issue is now resolved.

All services are back online. Still monitoring it for issues.