AS947

AS947 had four IPv4 prefixes and no IPv6 prefixes in the combined Route Views observation at 2026-10-23 22:00 UTC. The sample contains two AS_PATH neighbours, AS3356 and AS10796. This establishes routing visibility in that snapshot, but does not identify the ASN’s operator or establish commercial peering, upstream, customer, or provider relationships.

The combined observation estimates 1,024 IPv4 addresses. Route Views used the route-views2 and route-views6 collectors; these are aggregate counts across both, not separate counts attributed to either collector. Zero IPv6 prefixes means none were observed in this snapshot, not that the ASN is inactive or lacks IPv6 deployment at other times.

IANA lists AS947 within resource range 1–1876 as assigned by ARIN. That identifies the allocating RIR for the block, not an individual assignment record or the organization using this ASN. For identification or incident triage, compare the relevant observed prefix and timestamp with current routing data and seek an authoritative record explicitly linking an organization to AS947. Do not infer ownership or safety from the routing counts or neighbours alone.

Routing observation

Four IPv4 prefixes, zero IPv6 prefixes, and two sampled AS_PATH neighbours were present in the combined Route Views snapshot at 2026-10-23 22:00 UTC.

Identity

Operator and country are unknown from the supplied evidence.

Triage

Use the observed prefixes and timestamp to investigate a specific route; these counts do not establish ownership, activity outside the snapshot, or safety.

Observation scope

combined RouteViews snapshot at 2026-10-23T22:00:00.000Z; route-views2, route-views6 [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261023.2200.bz2