User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Firecrawl down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → firecrawl.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 420 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:30 | 0 | 0.0 | 609 ms | 0 |
| 10:30 | 0 | 0.0 | 286 ms | 0 |
| 12:30 | 0 | 0.0 | 464 ms | 0 |
| 14:45 | 0 | 0.0 | 671 ms | 0 |
| 16:45 | 0 | 0.0 | 3652 ms | 0 |
| 18:45 | 0 | 0.0 | 413 ms | 0 |
| 20:45 | 0 | 0.0 | 481 ms | 0 |
| 22:00 | 0 | 0.0 | 302 ms | 0 |
| 00:00 | 0 | 0.0 | 374 ms | 0 |
| 02:00 | 0 | 0.0 | 283 ms | 0 |
| 04:15 | 0 | 0.0 | 306 ms | 0 |
| 06:15 | 0 | 0.0 | 420 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Firecrawl badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Firecrawl yet. Outages of 10 minutes or more get their own page here.
Having trouble with Firecrawl?
One report per service every 10 minutes from this network. No account.
Follow Firecrawl
Get an email when Firecrawl goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Firecrawl alerts to Slack, Discord or a webhook — free.
About Firecrawl
Firecrawl is listed in our AI category and checked at firecrawl.dev. Supercharge your AI agents with data from the web and beyond. Building the library for superintelligence. 🔥
Firecrawl publishes an official status page at status.firecrawl.dev; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 688 ms average, 283–3652 ms range across 12 successful checks.
Questions
Is Firecrawl down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Firecrawl last down?
We have not recorded a public Firecrawl incident since monitoring began 8 days ago.
What is Firecrawl's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Firecrawl respond?
688 ms on average over the last 24 hours (283–3652 ms).
Does Firecrawl have an official status page?
Yes, at https://status.firecrawl.dev.
Firecrawl not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Firecrawl here at once, the problem is on Firecrawl's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Firecrawl. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.