Autonomous System Response Fields
Lookups on the API for any Autonomous System (AS) come with the following fields. Every JSON payload inherently contain every field. If a specific value cannot be determined, the field value is set to null.
| Field | Description |
|---|---|
| allocated | The date and time when the Autonomous System was allocated, presented in ISO 8601 format. |
| asn | The Autonomous System Number (ASN) that uniquely identifies an Autonomous System on the Internet. |
| country_code | The country in which the resource holder is legally based, presented in ISO 3166-1 alpha-2 format. This may not correspond to where the IP addresses are used. |
| domain | The top-level domain name associated with the AS that owns the connection IP. |
| name | The name of the organization that owns the Autonomous System. |
| prefixes → ipv4_count | The number of IPv4 addresses announced by the Autonomous System. |
| prefixes → ipv6_count | The number of IPv6 addresses announced by the Autonomous System. |
| prefixes → ipv4 | The list of IPv4 prefixes announced by the Autonomous System. |
| prefixes → ipv6 | The list of IPv6 prefixes announced by the Autonomous System. |
| prefixes → ipv4/ipv6 → cidr | The Classless Inter-Domain Routing notation representing a specific IP address block. This notation indicates the starting IP address and the subnet mask, providing details about the range and size of the address block. |
| prefixes → ipv4/ipv6 → country_code | The two-letter country code (in ISO 3166-1 alpha-2 format) representing the legal location for the given IP address block. This may not correspond to where the IP addresses are used. |
| prefixes → ipv4/ipv6 → network_name | A reasonably descriptive name as it appears in Whois. It consists of capitals, dashes ("-") and digits, but must start with a capital. |
| prefixes → ipv4/ipv6 → organization | A short name or description of the organization that uses the prefix. |
| prefixes → ipv4/ipv6 → registry | The Regional Internet Registry (RIR) responsible for allocating and registering the IP prefix. Possible values are AFRINIC, APNIC, ARIN, LACNIC, or RIPE_NCC. |
| prefixes → ipv4/ipv6 → status | The current assignment status of the IP address block, indicating its allocation purpose and whether it can be transferred between service providers. The specific set of status values can vary depending on the regional internet registry (RIR) responsible for the address space. |
| prefixes → ipv4/ipv6 → size | The total number of IP addresses contained within the specified CIDR block. |
| relationships → downstreams | A list of ASNs that primarily receive their Internet traffic from the current Autonomous System. Downstream networks are typically smaller networks or customers to which the current AS provides Internet access or transit services, enabling them to connect to a broader range of the Internet. |
| relationships → peers | A list of ASNs that maintain a mutual agreement with this Autonomous System to exchange traffic directly, typically for the purpose of improving efficiency and reducing the reliance on upstream providers. Peering relationships are established to facilitate direct exchange of traffic between networks, often without monetary exchange. |
| relationships → upstreams | A list of ASNs from which the current Autonomous System primarily receives its internet traffic. An upstream provider is typically a larger network or Internet Service Provider (ISP) to which the current AS pays for internet access or transit services, allowing the AS to reach parts of the Internet outside of its direct peers or local connections. |
| registry | The Regional Internet Registry (RIR) to which the Autonomous System is registered. Possible values are AFRINIC, APNIC, ARIN, LACNIC, or RIPE_NCC. |
| type | Classifies the AS usage type among business, education, government, hosting, inactive, and isp. |
| updated | The date and time when the Autonomous System record was last updated, presented in ISO 8601 format. |