AS993

AS993's operator is unknown; it was visible in the sampled routing snapshot with two IPv4 prefixes and one IPv6 prefix.

The combined observation from Route Views route-views2 and route-views6 is dated 2026-10-25 20:00 UTC. It contains two IPv4 prefixes, one IPv6 prefix, an IPv4 address estimate of 8,192, and one observed AS_PATH neighbor: AS46997. The neighbor is not verified as a commercial peer or upstream.

These route counts describe that snapshot only. They do not establish who operates AS993, where it is located, who was assigned its resources, whether it is legitimate, or whether it carries traffic. The IANA entry places ASN 993 in resource block 1-1876 and says that block is assigned by ARIN; this does not identify an individual assignee.

For identification, compare the announced prefixes and AS_PATHs against dated registry and routing records, then seek first-party documentation that explicitly links an organization to AS993. Treat AS46997 only as an observed path neighbor, and do not infer a provider relationship from this single combined observation.

Routing snapshot

Two IPv4 prefixes and one IPv6 prefix were observed in the combined Route Views snapshot dated 2026-10-25 20:00 UTC.

Observed neighbor

AS46997 appeared as an AS_PATH neighbor; this does not verify a peer or upstream relationship.

Triage

Operator identity and security status are unknown from the supplied evidence; routing presence alone does not establish legitimacy or malicious use.

RIR

ARIN [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

Observation scope

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

ASN

993 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

IANA resource block

1-1876 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv

IPv4 prefix count

2 [Combined observation across Route Views route-views2 and route-views6 RIBs at 2026-10-25 20:00 UTC; not a separate count per collector] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2; https://archive.routeviews.org/route-views6/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2

IPv4 address estimate

8192 [Combined observation across Route Views route-views2 and route-views6 RIBs at 2026-10-25 20:00 UTC; estimate of announced address space, not observed hosts or traffic] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2; https://archive.routeviews.org/route-views6/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2

IPv6 prefix count

1 [Combined observation across Route Views route-views2 and route-views6 RIBs at 2026-10-25 20:00 UTC; not a separate count per collector] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2; https://archive.routeviews.org/route-views6/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2

Observed AS_PATH neighbor

AS46997 [Combined observation across Route Views route-views2 and route-views6 RIBs at 2026-10-25 20:00 UTC; AS_PATH adjacency, not evidence of commercial peering or an upstream relationship] — https://archive.routeviews.org/route-views2/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2; https://archive.routeviews.org/route-views6/bgpdata/2026.10/RIBS/rib.20261025.2000.bz2