> For the complete documentation index, see [llms.txt](https://docs.bfore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bfore.ai/docs/console/takedowns-list/takedown-statuses.md).

# Takedown statuses and lifecycle

Takedowns show two levels of status: a simple status chip, and a more detailed **Process phase**.

## Status chips

<table><thead><tr><th width="177.8125">Chip</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Under review</strong></td><td>PreCrime is reviewing the submission before acting on it. This applies to social media and user-reported (external threat domain) takedowns, which require this check since they weren't identified by PreCrime.</td></tr><tr><td><strong>In progress</strong></td><td>The takedown is approved and being worked, moving through escalation phases. This includes cases where the responsible third party has not yet responded (Final Escalation).</td></tr><tr><td><strong>Completed</strong></td><td>The infrastructure was successfully taken down.</td></tr><tr><td><strong>Cancelled</strong></td><td>Your team cancelled the takedown. Click the chip to see the reason.</td></tr><tr><td><strong>Rejected</strong></td><td>The request was declined by PreCrime. Click the chip to see the reason.</td></tr><tr><td><strong>Not started</strong></td><td>No takedown exists for this attack yet.</td></tr></tbody></table>

## Process phases

While a takedown is in progress, the **Process phase** field shows the detailed stage:

1. **Pending Approval** - awaiting review.
2. **Initial Phase** - first contact with the responsible parties.
3. **Level 1 - Escalation**, **Level 2 - Escalation**, **Level 3 - Escalation** - progressively stronger escalation when earlier steps do not resolve the takedown.
4. **Final Escalation** - the responsible third party (registrar, host, platform) has not responded; the takedown continues and remains open while BforeAI pursues further action.
5. **Reporting** and **Monitoring and Audit** - verification and follow-up stages.
6. Final outcome: **Successful**, **Cancelled**, or **Rejected**.

## Timing and results

* Completed takedowns show their total **Process Time** and completion date, so you can see exactly how long it took to neutralize each threat.
* The dashboard's **Takedown overview** widget tracks completed and ongoing counts plus the median resolution time, giving you a summary view of takedown performance across your account.
* **Cost saved** on a takedown card reflects your company's estimated cost per successful attack (configurable insight shown in [Company settings](/docs/console/account-settings/company-settings.md)).

The full step-by-step history of an individual takedown is visible in the **Attack lifecycle** timeline on the [attack detail page](/docs/console/disrupted-attacks/attack-details.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bfore.ai/docs/console/takedowns-list/takedown-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.