AS913
No prefixes for this AS number were observed in the RouteViews RIB.
Summary
- // analyst note
- No operator, prefixes, or CAIDA-inferred relationships found for AS913 as of 2026-08. RouteViews observed 0 IPv4 / 0 IPv6 prefixes and 0 neighboring ASNs on 2026-08-20; this is a single collector snapshot, not proof the ASN will never route. CAIDA AS Relationships (dataset date 2026-08-01, Public AUA) shows 0 inferred provider, customer, or peer relationships among published neighbours, a floor from unclassified data, not a census. RIR is ARIN, from the IANA AS Number registry range 1-1876. Operator identity, allocation date, RPKI status, exchange presence, and abuse contacts are all Unknown as of 2026-08.
- // security note
- NEUTRAL/DATED: No notable public abuse signal found for AS913 as of an August 2026 search across malware, spam, botnet, DDoS, bulletproof-hosting, BGP-hijack/route-leak, and NANOG/community-mention terminology.
About this ASN.
AS913 is an autonomous system number with no operator identified by any permitted source and no observed routing activity: the RouteViews route collector recorded zero originated prefixes for AS913 in its 2026-08-20 snapshot, and the CAIDA AS Relationships cache lists zero inferred provider, customer, or peer relationships for it as of its 2026-08-01 dataset. This reads as a dormant or unannounced allocation, not an active network.
Targeted searches for an AS913 peering policy, network/IR page, looking glass, or an operator's own NANOG/RIPE mailing-list post found no qualifying operator-published material. Third-party WHOIS/RDAP aggregators surfaced an unverified company name for AS913, but that is a third-party scrape of registry data, not first-party material naming the ASN, so it is not published here as the operator.
The IANA AS Number registry places AS913 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. Allocation date, RPKI validation posture, exchange-point presence, peering policy, and abuse contacts are all Unknown as of 2026-08. The routing figures above reflect a single collector's snapshot and a single relationship-inference dataset on separate dates, not a registry-declared allocation size or a permanent statement that this ASN will never route.
- Spamhaus
- Unknown — no public Spamhaus ASN-DROP listing or discussion of AS913 found via web search as of an August 2026 search; Spamhaus's own lookup tool was not queried directly — spamhaus.org.
- BGP incidents
- No reported BGP hijack, route leak, or routing-security incident naming AS913 found as of an August 2026 search.
- Community mentions
- No NANOG mailing-list thread or networking-community discussion mentioning AS913 found as of an August 2026 search — seclists.org/nanog, archive.nanog.org.
- CVE / malware
- No CVE, malware, or botnet command-and-control association naming AS913 found as of an August 2026 search.
- Operator
- Unknown — no operator-published material (own domain, IR page, peering policy, looking glass, or a NANOG/RIPE list post under an operator's own name) identifies the holder of AS913 as of an August 2026 search [Unknown]
- Country / RIR
- Country Unknown [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS913 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876
- Allocated
- Unknown [Unknown]
- Org status
- Unknown [Unknown]
- Contacts
- Unknown [Unknown]
Security/abuse context (NEUTRAL, DATED)
see the Security section above for abuse-signal, Spamhaus, BGP-incident, community, and CVE checks as of an August 2026 search
Network & routing
- Network type
- Unknown [Unknown]
- Size
- 0 IPv4 prefixes and 0 IPv6 prefixes originated — no row for AS913 found in the routing cache, as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS913
- Routing/peering
- 0 distinct neighboring ASNs observed by RouteViews on 2026-08-20. Relationship roles from the CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA): 0 inferred providers, 0 customers, 0 settlement-free peers among published neighbours — both columns of the cache were checked for an exact match on 913, and none was found. Peering policy: Unknown[Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS913, the cached registry snapshots/caida-as-rel.csv AS913
- RPKI
- Unknown — an unevaluated status, not a report of an absent or invalid ROA [Unknown]
- Notable usage
- Unknown [Unknown]
- Related ASNs
- Unknown — no permitted source ties another ASN to AS913 [Unknown]
- Related fields
- AS rank, customer cone size, IX presence, and peering policy are all Unknown [Unknown]
- Analyst note
- No operator, prefixes, or CAIDA-inferred relationships found for AS913 as of 2026-08. RIR is ARIN, from the IANA AS Number registry range 1-1876. Routing figures reflect a single RouteViews snapshot (2026-08-20) showing zero originated prefixes, and a single CAIDA relationship-inference dataset (2026-08-01) showing zero classified relationships — a floor from unclassified data, not proof of permanent dormancy. Allocation date, operator identity, RPKI status, exchange presence, and abuse contacts are Unknown as of 2026-08.