asn.dev

Observed topology

AS393227 RTC-NET

Residential ARIN Cable/DSL/ISP

Upstreams 6 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 6
Upstream graph Who carries AS393227, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS393227 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS393227: 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 IPv6339
AS3356Level 3 Parent, LLCTransitIPv4 IPv6290
AS6939Hurricane Electric LLCTransitIPv4 IPv6117
AS852TELUS Communications Inc.ResidentialIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv614
AS293ESnetUnclassifiedIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55230Pulaski White Rural Telephone Cooperative Inc.UnclassifiedIPv4 IPv6492
AS399356Kosciusko Connect LLCUnclassifiedIPv4234

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6807
AS55230Pulaski White Rural Telephone Cooperative Inc.UnclassifiedIPv4 IPv6661
AS3356Level 3 Parent, LLCTransitIPv4 IPv6577
AS6939Hurricane Electric LLCTransitIPv4 IPv6257
AS399356Kosciusko Connect LLCUnclassifiedIPv4234
AS852TELUS Communications Inc.ResidentialIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv614
AS293ESnetUnclassifiedIPv413

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.