> For the complete documentation index, see [llms.txt](https://docs.elastiflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elastiflow.com/data_platforms/elastic/ml/perf/asn_thruput.md).

# Unusual ASN Traffic Volume

Detecting an unusual volume of traffic to or from an Autonomous System (AS) is crucial for maintaining the integrity and performance of network infrastructures. An Autonomous System is a collection of IP routing prefixes under the control of one or more network operators that presents a common, clearly defined routing policy to the internet. Unusual traffic patterns involving an AS can be indicative of several issues, such as targeted cyberattacks, network hijacking, or unintentional misconfigurations leading to traffic floods or leaks. Identifying these anomalies promptly is essential for preventing potential network disruptions, mitigating security risks, and ensuring efficient network operation. Early detection allows network operators to take swift corrective actions to address the underlying causes and maintain the stability of their networks.

ElastiFlow provides a collection of anomaly detection jobs designed to identify unusual volumes of traffic to or from an Autonomous System that comprise various tools and techniques focused on monitoring and analyzing network traffic patterns.

## Attributes

| Attribute    | Information |
| ------------ | ----------- |
| **Analysis** | temporal    |

## Downloads

| Schema    | Endpoint        | Metric      | Link                                                                                                                                                                                |
| --------- | --------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **CODEX** | **source**      | **bytes**   | [elastiflow\_codex\_perf\_asn\_src\_thruput\_bytes](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_src_thruput_bytes.json)     |
| **CODEX** | **source**      | **packets** | [elastiflow\_codex\_perf\_asn\_src\_thruput\_packets](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_src_thruput_packets.json) |
| **CODEX** | **source**      | **flows**   | [elastiflow\_codex\_perf\_asn\_src\_thruput\_flows](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_src_thruput_flows.json)     |
| **CODEX** | **destination** | **bytes**   | [elastiflow\_codex\_perf\_asn\_dst\_thruput\_bytes](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_dst_thruput_bytes.json)     |
| **CODEX** | **destination** | **packets** | [elastiflow\_codex\_perf\_asn\_dst\_thruput\_packets](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_dst_thruput_packets.json) |
| **CODEX** | **destination** | **flows**   | [elastiflow\_codex\_perf\_asn\_dst\_thruput\_flows](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/codex/performance/perf_asn_dst_thruput_flows.json)     |
| **ECS**   | **source**      | **bytes**   | [elastiflow\_ecs\_perf\_asn\_src\_thruput\_bytes](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_src_thruput_bytes.json)         |
| **ECS**   | **source**      | **packets** | [elastiflow\_ecs\_perf\_asn\_src\_thruput\_packets](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_src_thruput_packets.json)     |
| **ECS**   | **source**      | **flows**   | [elastiflow\_ecs\_perf\_asn\_src\_thruput\_flows](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_src_thruput_flows.json)         |
| **ECS**   | **destination** | **bytes**   | [elastiflow\_ecs\_perf\_asn\_dst\_thruput\_bytes](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_dst_thruput_bytes.json)         |
| **ECS**   | **destination** | **packets** | [elastiflow\_ecs\_perf\_asn\_dst\_thruput\_packets](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_dst_thruput_packets.json)     |
| **ECS**   | **destination** | **flows**   | [elastiflow\_ecs\_perf\_asn\_dst\_thruput\_flows](https://github.com/elastiflow/elastiflow_for_elasticsearch/raw/master/ml/ecs/performance/perf_asn_dst_thruput_flows.json)         |

By implementing this suite of anomaly detection jobs, network administrators and security professionals can quickly identify unusual traffic patterns involving an Autonomous System. Early identification of these anomalies is key to taking timely actions to investigate and resolve potential issues, whether they are security-related, operational, or configuration-based. This proactive approach is vital for ensuring the ongoing security, performance, and reliability of network operations in the complex and dynamic environment of internet routing and traffic management.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.elastiflow.com/data_platforms/elastic/ml/perf/asn_thruput.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.