/bgptools/asns

POST /api/bgptools/asns

Price: 20 credits

Look up an Autonomous System's profile on bgp.tools by AS number

How to use it

Look up an Autonomous System (network) by its AS number and get its BGP profile: network name, website, registration date, the RIR handle and registry it is registered under, network status and type (Content / Eyeball / Transit …), the number of IPv4 and IPv6 prefixes it originates, its main upstream carriers, global and per-country rankings (AS cone, known peers, unique domains, estimated eyeballs, originated space), and classification tags (CDN, VPN host, DDoS mitigation, anycast, validating RPKI ROV, and more). Accepts a bare number (e.g. 13335) or an 'AS'-prefixed value (e.g. 'AS13335'). This is the central object most BGP and network-infrastructure lookups start from.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• asn union required — Autonomous System Number to look up (accepts a bare number or an 'AS'-prefixed value) (examples: "13335", "AS13335", 15169)

Response

• @type string (default: "BgptoolsAsn")
• asn integer required
• name string nullable
• website_url string nullable
• image string nullable
• registered_at string nullable
• rir_handle string nullable
• rir string nullable
• status string nullable
• network_type string nullable
• ipv4_prefix_count integer nullable
• ipv6_prefix_count integer nullable
• upstreams array (default: [])
  • @type string (default: "BgptoolsAsnRef")
  • asn integer required
  • name string nullable
• rankings array (default: [])
  • @type string (default: "BgptoolsAsnRanking")
  • rank integer required
  • metric string required
• tags array (default: [])
  • @type string (default: "BgptoolsTag")
  • slug string required
  • name string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Autonomous System Number not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.