asn.dev

Observed topology

AS20516 SV

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20516: 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
AS35297Dataline LLCUnclassifiedIPv4237
AS1820WNET TELECOM USA Corp.ResidentialIPv4167
AS43668"AS43668" LLCResidentialIPv4104
AS49824PC "Astra-net"ResidentialIPv462
AS6939Hurricane Electric LLCTransitIPv442
AS24482SG.GSHostingIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207488SQ TELECOM, LLCUnclassifiedIPv449
AS210092Rabchuk Valentyna ViktorivnaUnclassifiedIPv420

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv4286
AS1820WNET TELECOM USA Corp.ResidentialIPv4186
AS43668"AS43668" LLCResidentialIPv4105
AS49824PC "Astra-net"ResidentialIPv462
AS207488SQ TELECOM, LLCUnclassifiedIPv449
AS6939Hurricane Electric LLCTransitIPv442
AS210092Rabchuk Valentyna ViktorivnaUnclassifiedIPv420
AS24482SG.GSHostingIPv47

Provenance

Where this comes from

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