asn.dev

Observed topology

AS396930 OPUS-INTERACTIVE-VA1

Unclassified ARIN

Upstreams 4 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 5
Upstream graph Who carries AS396930, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS396930 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396930: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6102
AS6461Zayo BandwidthTransitIPv488
AS3356Level 3 Parent, LLCTransitIPv4 IPv675
AS12025Iron Mountain Data CenterUnclassifiedIPv67

Transit

Downstream networks

inferred

Networks for which AS396930 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS398031Joscor LLCUnclassifiedIPv4 IPv692
AS400554Stricity LLCUnclassifiedIPv4 IPv649
AS400510United Management Group, LLCHostingIPv433
AS14746NocTel Communications, Inc.UnclassifiedIPv430

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS396930 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4189
AS1299Arelion Sweden ABTransitIPv4 IPv6151
AS3356Level 3 Parent, LLCTransitIPv4 IPv6115
AS398031Joscor LLCUnclassifiedIPv4 IPv692
AS400554Stricity LLCUnclassifiedIPv4 IPv649
AS400510United Management Group, LLCHostingIPv433
AS14746NocTel Communications, Inc.UnclassifiedIPv430
AS12025Iron Mountain Data CenterUnclassifiedIPv621

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.