asn.dev

Observed topology

AS7381 SRS-6-Z-7381

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7381: 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
AS1828Unitas GlobalUnclassifiedIPv4 IPv67,484
AS1299Arelion Sweden ABTransitIPv4 IPv63,992
AS2914NTT America, Inc.TransitIPv4 IPv62,330

Transit

Downstream networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS19311Stewart TitleUnclassifiedIPv4182
AS20314Conagra Brands Inc.UnclassifiedIPv4180
AS35907NaviNet Inc.UnclassifiedIPv4121
AS22868BDP InternationalUnclassifiedIPv4120
AS26666Interserver, IncUnclassifiedIPv4 IPv6120
AS7148Graphnet, Inc.UnclassifiedIPv461
AS13620EMBLEMHEALTH SERVICES COMPANY, LLCUnclassifiedIPv461
AS18891Confluence TechnologiesUnclassifiedIPv461
AS23251Bridgestone Americas, Inc.UnclassifiedIPv461
AS23280Venn Technology CorpUnclassifiedIPv461

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS1828Unitas GlobalUnclassifiedIPv4 IPv68,348
AS1299Arelion Sweden ABTransitIPv4 IPv64,446
AS2914NTT America, Inc.TransitIPv4 IPv62,622
AS19311Stewart TitleUnclassifiedIPv4182
AS20314Conagra Brands Inc.UnclassifiedIPv4180
AS26666Interserver, IncUnclassifiedIPv4 IPv6141
AS35907NaviNet Inc.UnclassifiedIPv4121
AS22868BDP InternationalUnclassifiedIPv4120
AS7148Graphnet, Inc.UnclassifiedIPv461
AS13620EMBLEMHEALTH SERVICES COMPANY, LLCUnclassifiedIPv461

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.