AS900
AS900 announces 1 IPv4 and 0 IPv6 prefixes and peers with 2 other networks.
Summary
- // analyst note
- Small, lightly routed network: RouteViews observed 1 IPv4 prefix (256 addresses) and 0 IPv6 prefixes for AS900 at 2026-08-20T00:00:00Z, with 2 neighbouring ASNs (AS6327, AS7122) — the full observed set, not a capped sample. CAIDA's AS Relationships dataset (dataset date 2026-08-01) carries no classification involving AS900, so upstream/customer/peer direction is unclassified rather than a measured zero. The IANA AS Numbers registry places AS900 within the 1-1876 block, assigned by ARIN — that row fixes the administering RIR only, not a per-ASN assignment class. No operator-published source names who operates AS900, so operator identity, network type, country, and allocation date remain Unknown.
- // security note
- NEUTRAL/DATED: No notable public abuse signal found for AS900 as of 2026-08-22.
About this ASN.
AS900 is a lightly routed autonomous system whose operator has not been identified by any permitted source. RouteViews observed it originating a single, small IPv4 prefix as of 2026-08-20, and no operator-published page, RIR-permitted registry field, or community record names who runs it, so operator identity and network type stay Unknown.
As observed by RouteViews at 2026-08-20T00:00:00Z (route-views2/route-views6), AS900 originated 1 IPv4 prefix — 256 addresses — and 0 IPv6 prefixes. The collector recorded 2 neighboring ASNs, AS6327 and AS7122, which is the full observed set rather than a capped sample. This reflects one collector's snapshot at one instant, not a census of the network.
CAIDA's AS Relationships dataset (dataset date 2026-08-01) carries no classification involving AS900 as either party, so upstream, customer, and peer direction are all unclassified rather than a measured zero. A pair CAIDA does not classify is simply absent from its cache, not confirmed to hold no relationship.
The IANA AS Numbers registry places AS900 inside the 1-1876 block, assigned by ARIN. That row fixes only the administering RIR — it does not establish a per-ASN assignment class, so assignment class stays Unknown. Forward searches across peering-policy pages, looking-glass tools, NANOG and RIPE mailing-list archives, and abuse-contact directories located no operator-own-domain material naming AS900, so operator, legal name, website, country, and allocation date remain Unknown.
- Abuse signal
- No notable public abuse signal found for AS900 as of 2026-08-22, across a general web search for spam/malware/botnet/hijack terms and the Spamhaus ASN-DROP list — spamhaus.org.
- Spamhaus ASN-DROP
- AS900 does not appear on the Spamhaus ASN-DROP list as of 2026-08-22 (439 records checked, none for ASN 900) — spamhaus.org/drop/asndrop.json.
- Community archives
- No NANOG or RIPE mailing-list threads referencing AS900 found in mailman.nanog.org, archive.nanog.org, or seclists.org's NANOG mirror as of an August 2026 search.
- CVE / malware
- No CVE, malware, or botnet command-and-control association naming AS900 found as of an August 2026 search.
- Operator
- Unknown — no operator-published source (own domain, IR page, peering policy, looking glass, or NANOG/RIPE list post) names AS900 after multiple forward searches [Unknown]
- Country / RIR
- Country Unknown [Unknown]. RIR: ARIN, per the IANA AS Numbers registry (block 1-1876, assigned by ARIN) [Confirmed] — the IANA Autonomous System Number registry (row: 1-1876, Assigned by ARIN)
- Allocated
- Unknown [Unknown]
- Org status
- Unknown — no operator-published or permitted registry source confirms operating status [Unknown]
- Contacts
- Unknown [Unknown]
Security/abuse context (NEUTRAL, DATED)
see the Security section above; no notable abuse signal found as of 2026-08-22
Network & routing
- Network type
- Unknown — no operator-published material found [Unknown]
- Size
- 1 IPv4 prefix (256 addresses), 0 IPv6 prefixes, as observed by RouteViews at 2026-08-20T00:00:00Z [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS900, the cached registry snapshots/manifest.json (the RouteViews BGP routing data (CC BY 4.0): rib.20260820.0000.bz2, route-views2 / route-views6)
- Routing/peering
- 2 neighboring ASNs observed by RouteViews at 2026-08-20T00:00:00Z — AS6327 and AS7122, the full observed set (not a capped sample). CAIDA's AS Relationships cache (dataset date 2026-08-01) carries no classification for AS900, so upstream/customer/peer direction is unclassified, not a measured zero [Confirmed for the neighbor observation; Unknown for relationship direction] — the RouteViews BGP routing data (CC BY 4.0) AS900, the cached registry snapshots/caida-as-rel.csv
- 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]
- Assignment class
- Unknown — the IANA row fixes the administering RIR only, not a per-ASN assignment class; no other permitted source establishes one [Unknown]
- Related fields
- AS rank, customer cone size, and MANRS membership are all Unknown [Unknown]
- Analyst note
- AS900 is a small, lightly routed network — 1 IPv4 prefix (256 addresses) and 0 IPv6 prefixes, with 2 neighboring ASNs (AS6327, AS7122), per RouteViews at 2026-08-20. CAIDA carries no relationship classification for it as of its 2026-08-01 dataset (unclassified, not a measured zero). The IANA AS Numbers registry lists it as assigned by ARIN within block 1-1876, which fixes the administering RIR only, not a per-ASN assignment class. No operator-published source establishes operator identity, network type, country, or allocation date; all remain Unknown.
What this network routes.
- 207.174.10.0/24
Who it talks to.
Neighbours observed by RouteViews at 2026-09-20, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.
| ASN | Operator | Role |
|---|---|---|
| AS6327 | — | — |
| AS7122 | — | — |