Autonomous system detail

AS923

Announced

AS923 announces 2 IPv4 and 2 IPv6 prefixes and peers with 1 other networks.

Summary

// analyst note
Small, actively routed ASN: RouteViews observed 2 IPv4 / 2 IPv6 prefixes and 1 neighboring ASN (AS26073) on 2026-08-20; this is a single collector snapshot, not a registry-declared allocation size. CAIDA AS Relationships (dataset date 2026-08-01) carries no row for AS923 as either party, so the AS26073 adjacency is unclassified, not a confirmed customer/upstream/peer link. No operator-published source names AS923 as of an August 2026 search; identity fields stay null rather than inferred from mirrored registry data. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown as of 2026-08.
// security note
NEUTRAL/DATED: No ASN-wide blocklisting found (Spamhaus SBL/ASN-DROP, AbuseIPDB, abuse.ch/URLhaus, github.com/C0nw0nk/ASN-BlackList) as of an August 2026 search.
IPv4 prefixes
2
~1.3K addresses
IPv6 prefixes
2
announced
Peer networks
1
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

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

AS923 is a small, actively routed autonomous system whose operator is not identified by any operator-published source found in an August 2026 search. As observed by the RouteViews route collector at 2026-08-20T00:00:00Z, it originates 2 IPv4 prefixes and 2 IPv6 prefixes, together estimated at 1,280 IPv4 addresses, with exactly one neighboring ASN observed in the same dump — a small, single-homed footprint, not a dormant or unrouted registration.

That single neighbor, AS26073, reflects undirected AS-path adjacency rather than a classified customer, upstream, or peer relationship. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row for AS923 on either side, so no provider, customer, or peer can be inferred for this ASN among published neighbours; the link to AS26073 is simply unclassified, not evidence of zero real-world relationships.

Searches for an operator-published network page, peering policy, looking-glass, or a NANOG/RIPE list post under an operator's own name naming AS923 turned up nothing that qualifies. A candidate company name recurred across search results, but every occurrence traced back to third-party ASN-lookup or BGP-aggregator pages republishing registry data, not to material the party itself published; a direct connection attempt to that candidate's own domain failed at the network level, so no self-published page could be inspected either way. A NANOG post surfaced by a similar query turned out on inspection to discuss an unrelated, numerically adjacent ASN, not AS923, and was discarded.

With no operator-published source binding a name to AS923, operator, as_name, website, network_type, country, and org_status all stay Unknown. The IANA AS Number registry places AS923 in the 1-1876 range recorded as "Assigned by ARIN," so its administering RIR is ARIN; allocation date is Unknown.

Exposure
Minimal — the ASN originates only 2 IPv4 and 2 IPv6 prefixes with a single observed neighbor (AS26073), a small footprint as of the 2026-08-20 RouteViews observation.
Blocklist status
No listing found in Spamhaus SBL or ASN-DROP, AbuseIPDB, abuse.ch/URLhaus, or a community-maintained ASN blacklist (github.com/C0nw0nk/ASN-BlackList) naming AS923, as of an August 2026 search.
Community signal
No NANOG mailing-list or meeting-archive thread, Reddit networking discussion, or public outage report naming AS923 was found, as of an August 2026 search.
Hijack / leak / botnet
No public reporting of route hijacking, route leaks, or botnet/DDoS association with AS923 was found, as of an August 2026 search.
CVE / threat report
Unknown — a targeted CVE or named threat-intelligence search specific to AS923 was not completed, as of an August 2026 search.
Operator
Unknown — no operator-published source names AS923; recurring third-party mentions trace only to ASN-lookup/BGP-aggregator mirrors of registry data, not to operator-published material [Unknown]
Country / RIR
Country Unknown [Unknown]. RIR: ARIN — the IANA AS Number registry records the 1-1876 range containing AS923 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 exposure, blocklist, community, hijack/leak, and CVE checks as of an August 2026 search

Network & routing

Network type
Unknown [Unknown]
Size
2 IPv4 prefixes and 2 IPv6 prefixes originated; an estimated 1,280 IPv4 addresses, as observed by RouteViews on 2026-08-20 [Confirmed] — the RouteViews BGP routing data (CC BY 4.0) AS923
Routing/peering
1 distinct neighboring ASN (AS26073) observed by RouteViews on 2026-08-20 — the full observed set, not a capped sample; this is undirected AS-path adjacency, not a customer/upstream/peer classification. The CAIDA AS Relationships cache (dataset date 2026-08-01) carries no row for AS923 as either party, so 0 providers, 0 customers, and 0 peers are inferred among published neighbours — a floor, not a census. Peering policy: Unknown [Confirmed for the neighbor count and the CAIDA absence; Unknown for policy] — the RouteViews BGP routing data (CC BY 4.0) AS923, 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 [Unknown]
Related ASNs
Unknown — the single observed neighbor AS26073 carries no classified relationship to AS923 [Unknown] — the RouteViews BGP routing data (CC BY 4.0) AS923
Related fields
AS rank, customer cone size, and MANRS membership are all Unknown [Unknown]
Analyst note
Small, actively routed ASN with a single observed neighbor and no CAIDA-classified relationship. No operator-published source binds a name to AS923 as of an August 2026 search; recurring third-party mentions trace only to registry-data mirrors, and a candidate operator's own domain could not be reached to check for a self-published page. RIR is ARIN, from the IANA AS Number registry range 1-1876. Allocation date, RPKI status, IX presence, and abuse contacts are Unknown as of 2026-08.
[ 02 ] — Announced prefixes

What this network routes.

4 prefixes total · as observed by RouteViews at 2026-09-20 · one collector view, not a global census
// IPv4 prefixes2
  1. 131.143.204.0/22/22
  2. 23.144.156.0/24/24
// IPv6 prefixes2
  1. 2602:fbf5:3::/48/48
  2. 2602:fbf5::/48/48
[ 03 ] — Notable peers & upstreams

Who it talks to.

1 observed neighbour
// Notable connections1 of 1 observed

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.

ASNOperatorRole
AS26073 — —
Neighbours observed via public BGP collectors; not a complete peering list.