- Detected by Pingoru
- Sep 15, 2026, 02:04 PM UTC
- Resolved
- Sep 15, 2026, 02:50 PM UTC
- Duration
- 46m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Sep 15, 2026, 02:04 PM UTC
We are seeing a latency degradation on /scrape. We are investigating
-
resolved Sep 15, 2026, 02:50 PM UTC
/scrape has recovered. We will continue to monitor and make improvements.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2026, 01:45 AM UTC
- Resolved
- Sep 06, 2026, 01:52 AM UTC
- Duration
- 7m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Sep 06, 2026, 01:45 AM UTC
We are investigating.
-
resolved Sep 06, 2026, 01:52 AM UTC
The incident has been resolved. Apologies for the inconvenience. We will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 07:12 AM UTC
- Resolved
- Sep 03, 2026, 07:28 AM UTC
- Duration
- 16m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Sep 03, 2026, 07:12 AM UTC
We are investigating
-
resolved Sep 03, 2026, 07:28 AM UTC
Between 07:12 and 07:28 UTC today, a network issue in our upstream ISP caused a portion of jobs to fail. The issue resolved at 07:28 UTC and we are working on additional redundancy to avoid similar issues in the future.
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2026, 06:00 AM UTC
- Resolved
- Aug 27, 2026, 06:56 AM UTC
- Duration
- 56m
Affected: Current status by service (api.firecrawl.dev)Current status by service (firecrawl.dev)
Timeline · 2 updates
-
investigating Aug 27, 2026, 06:00 AM UTC
/interact API calls using the prompt functionality are failing. We are investigating.
-
resolved Aug 27, 2026, 06:56 AM UTC
All affected features are now working. Apologies for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 07:20 AM UTC
- Resolved
- Jul 20, 2026, 08:04 AM UTC
- Duration
- 44m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jul 20, 2026, 07:20 AM UTC
We are investigating
-
resolved Jul 20, 2026, 08:04 AM UTC
The /interact and /browser APIs have fully recovered and are operating normally. The outage was caused by an issue at an upstream provider, which has since been resolved. All other Firecrawl APIs remained unaffected throughout the incident.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 02:01 AM UTC
- Resolved
- Jun 19, 2026, 02:32 AM UTC
- Duration
- 31m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jun 19, 2026, 02:01 AM UTC
A portion of PDF scraping is currently degraded, we are investigating.
-
resolved Jun 19, 2026, 02:32 AM UTC
The incident is now resolved, and we are taking steps to ensure it does not recur. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 05:56 PM UTC
- Resolved
- Jun 18, 2026, 10:52 PM UTC
- Duration
- 4h 56m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jun 18, 2026, 05:56 PM UTC
The screenshot format on scrape was degraded starting 10:56AM PDT.
-
resolved Jun 18, 2026, 10:52 PM UTC
This issue was resolved at 3:52PM PDT.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 02:55 PM UTC
- Resolved
- Jun 15, 2026, 03:45 PM UTC
- Duration
- 50m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jun 15, 2026, 02:55 PM UTC
Our /interact and /browser APIs are currently unavailable due to an outage at an upstream provider. We are monitoring the situation
-
resolved Jun 15, 2026, 03:45 PM UTC
The API has recovered.
Read the full incident report →
- Detected by Pingoru
- May 01, 2026, 05:04 AM UTC
- Resolved
- May 01, 2026, 05:04 AM UTC
- Duration
- —
Affected: Current status by service (api.firecrawl.dev)Current status by service (firecrawl.dev)
Timeline · 1 update
-
resolved May 01, 2026, 05:04 AM UTC
We’re back! API and dashboard should be up and running. Thanks for bearing with us.
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 07:35 PM UTC
- Resolved
- Apr 19, 2026, 08:07 PM UTC
- Duration
- 32m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Apr 19, 2026, 07:35 PM UTC
We are investigating.
-
resolved Apr 19, 2026, 08:07 PM UTC
Everything should be working now. We are still monitoring it.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 05:16 PM UTC
- Resolved
- Mar 31, 2026, 06:54 PM UTC
- Duration
- 1h 38m
Affected: Current status by service (firecrawl.dev)
Timeline · 2 updates
-
investigating Mar 31, 2026, 05:16 PM UTC
Switching teams and creating new user accounts are failing. We are investigating. API is unaffected.
-
resolved Mar 31, 2026, 06:54 PM UTC
The issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 08:09 PM UTC
- Resolved
- Mar 06, 2026, 08:21 PM UTC
- Duration
- 12m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Mar 06, 2026, 08:09 PM UTC
We are investigating
-
resolved Mar 06, 2026, 08:21 PM UTC
The issue has been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 01:17 AM UTC
- Resolved
- Jan 16, 2026, 01:26 AM UTC
- Duration
- 9m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jan 16, 2026, 01:17 AM UTC
We are investigating.
-
resolved Jan 16, 2026, 01:26 AM UTC
Services have been restored to full capacity. We are looking into the cause of the issue.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 04:17 PM UTC
- Resolved
- Jan 09, 2026, 04:26 PM UTC
- Duration
- 9m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Jan 09, 2026, 04:17 PM UTC
We are seeing intermittent failures of the queuing system powering Crawl and Batch Scrape. We are working on a resolution.
-
resolved Jan 09, 2026, 04:26 PM UTC
We have applied a fix and the issue should now be resolved. We are continuing to monitor the situation closely.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2025, 10:25 AM UTC
- Resolved
- Dec 18, 2025, 10:51 AM UTC
- Duration
- 26m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Dec 18, 2025, 10:25 AM UTC
We're seeing an elevated error rate on the Search endpoint. We are investigating.
-
resolved Dec 18, 2025, 10:51 AM UTC
The issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 03:12 AM UTC
- Resolved
- Dec 02, 2025, 03:15 AM UTC
- Duration
- 2m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 3 updates
-
investigating Dec 02, 2025, 03:12 AM UTC
api.firecrawl.dev is degraded.
-
resolved Dec 02, 2025, 03:15 AM UTC
The API issues have been resolved. An update to our ingress had caused incorrect SSL certificates to be served, but the correct certificates have now been applied.
-
resolved Dec 02, 2025, 03:15 AM UTC
The API issues have been resolved. An update to our ingress had caused incorrect SSL certificates to be served, but the correct certificates have now been applied.
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2025, 12:00 PM UTC
- Resolved
- Nov 07, 2025, 03:55 PM UTC
- Duration
- 3h 55m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Nov 07, 2025, 12:00 PM UTC
We are experiencing elevated database-related errors. We are investigating.
-
investigating Nov 07, 2025, 03:55 PM UTC
We are seeing complete system recovery. We will continue to monitor the system.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 11:36 PM UTC
- Resolved
- Nov 07, 2025, 12:14 AM UTC
- Duration
- 38m
Affected: Current status by service (api.firecrawl.dev)
Timeline · 2 updates
-
investigating Nov 06, 2025, 11:36 PM UTC
Timeouts are elevated. We are working on the issue.
-
resolved Nov 07, 2025, 12:14 AM UTC
The issue has been resolved.
Read the full incident report →