asn.dev

Observed topology

AS14380 OPUS-INTERACTIVE-HIO1

Hosting ARIN Content

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS14380: 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
AS6461Zayo BandwidthTransitIPv4 IPv693
AS6939Hurricane Electric LLCTransitIPv4 IPv666
AS1299Arelion Sweden ABTransitIPv4 IPv662
AS3356Level 3 Parent, LLCTransitIPv461
AS20055Wholesail networks LLCResidentialIPv420
AS9002RETN LimitedUnclassifiedIPv49
AS3130RGnet OUUnclassifiedIPv45
AS7575Australian Academic and Research Network (AARNet)EducationIPv45
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398031Joscor LLCUnclassifiedIPv4 IPv689
AS55226Wellpartner, IncUnclassifiedIPv458
AS36791Portland Internet Hosting LLCHostingIPv4 IPv640
AS400510United Management Group, LLCHostingIPv4 IPv618

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6123
AS20055Wholesail networks LLCResidentialIPv4 IPv6100
AS3356Level 3 Parent, LLCTransitIPv495
AS6461Zayo BandwidthTransitIPv4 IPv693
AS398031Joscor LLCUnclassifiedIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv680
AS55226Wellpartner, IncUnclassifiedIPv458
AS36791Portland Internet Hosting LLCHostingIPv4 IPv640
AS400510United Management Group, LLCHostingIPv4 IPv618
AS9002RETN LimitedUnclassifiedIPv413

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.