Autonomous system detail

AS915

Not announced

No prefixes for this AS number were observed in the RouteViews RIB.

Summary

// analyst note
Dormant, unannounced autonomous system: RouteViews observed 0 IPv4 / 0 IPv6 prefixes and 0 neighboring ASNs at 2026-08-20T00:00:00Z, a genuine none-observed result. CAIDA AS Relationships (dataset date 2026-08-01) resolves no relationship data for AS915 in either direction, which is unclassified rather than a confirmed absence of upstreams, customers, or peers. No operator-published source names an operator for AS915; third-party ASN-directory listings do not meet the provenance bar and are excluded. RIR is ARIN, from the IANA AS Number registry range 1-1876; IANA supplies no finer assignment class and no per-ASN allocation date for this range.
// security note
NEUTRAL/DATED: No ASN-wide blocklisting found (Spamhaus DROP/ASN-DROP) as of an August 2026 search.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
—
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Low  ·  3 sources  ·  How this page is checked

AS915 is a dormant autonomous system: as observed by the RouteViews route collector at 2026-08-20T00:00:00Z, it originates zero IPv4 prefixes and zero IPv6 prefixes, with zero neighboring ASNs seen in the same observation. No permitted source identifies who currently operates it.

This is a genuine none-observed result from a real collector query, not a lookup failure or a gap in the data. A dormant ASN can still be a valid, registered allocation that simply is not announcing routes at this moment, or has never announced routes at all; the RouteViews snapshot cannot distinguish those cases, it only reports what the collectors see.

The CAIDA AS Relationships cache (dataset date 2026-08-01) likewise resolves no relationship data for AS915 in either direction — neither as a subject nor as a counterparty. That is an unclassified result, not a confirmed absence of upstreams, customers, or peers; CAIDA infers relationships only from AS paths it observes, and an ASN with no announced routes generates no such paths to infer from.

Operator identity is Unknown. No operator-published material — a company's own domain, an investor-relations or peering-policy page, a looking glass, or a NANOG/RIPE mailing-list post under an operator's own name — names AS915 as its own. Search results returned only third-party ASN-lookup and IP-intelligence directories, which republish registry data rather than originate it, so they do not meet the bar for attributing this ASN to any organization. As of an August 2026 search, no such attribution can be made from permitted sources.

The IANA AS Number registry places AS915 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN. IANA supplies only that block-level administering-RIR designation for this range, not a finer assignment class and not a per-ASN allocation date, so both remain Unknown.

Blocklist status
No Spamhaus DROP/ASN-DROP listing found for AS915 as of an August 2026 search.
CVE / malware
No CVE, malware, or botnet command-and-control association naming AS915 found as of an August 2026 search.
Community signal
No NANOG mailing-list thread or archived post referencing AS915 found as of an August 2026 search.
Routing exposure
Zero prefixes are currently observed as originated by AS915, so it presents no active announced-route hijack or leak surface as of the 2026-08-20 RouteViews snapshot; this describes present routing behavior, not a security guarantee.
Operator
Unknown — no operator-published source (own domain, investor page, peering-policy page, looking glass, or NANOG/RIPE list post under the operator's own name) names AS915; third-party ASN-directory listings do not meet the provenance bar [Unknown]
Country / RIR
Country Unknown [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS915 as "Assigned by ARIN" [Confirmed] — the IANA Autonomous System Number registry 1-1876
Allocated
Unknown [Unknown]
Org status
Unknown — no operator-published material identifies a registrant organization [Unknown]
Contacts
Unknown [Unknown]

Security/abuse context (NEUTRAL, DATED)

see the Security section above — no blocklist, CVE, malware, or community-list signal found as of an August 2026 search

Network & routing

Network type
Unknown — no operator-published material describes this network [Unknown]
Size
0 IPv4 prefixes and 0 IPv6 prefixes originated; an estimated 0 IPv4 addresses, as observed by RouteViews at 2026-08-20T00:00:00Z — a genuine none-observed result, not a lookup error [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS915
Routing/peering
0 neighboring ASNs observed by RouteViews at 2026-08-20T00:00:00Z [Confirmed]. The CAIDA AS Relationships cache (dataset date 2026-08-01, CAIDA Public AUA) resolves no relationship at all for AS915, checked both as a subject and as a counterparty — unclassified, not a confirmed absence of upstreams/customers/peers
[Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS915, the cached registry snapshots/caida-as-rel.csv AS915
RPKI
Unknown — an unevaluated status, not a report of an absent or invalid ROA [Unknown]
Notable usage
Unknown — no operator-published material found [Unknown]
Related ASNs
None found [Unknown]
Related fields
AS rank, customer cone size, and MANRS membership are all Unknown [Unknown]
Analyst note
Dormant, unannounced ASN as observed by RouteViews at 2026-08-20T00:00:00Z (0 IPv4/IPv6 prefixes, 0 neighbors); CAIDA resolves no relationship data for it (dataset date 2026-08-01). No operator-published source names an operator for AS915, so operator, as_name, country, and related identity fields are Unknown. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, exchange presence, and abuse contacts are Unknown as of 2026-08.
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · as observed by RouteViews at 2026-09-20 · one collector view, not a global census
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.