asn.dev

Observed topology

AS20911 NETSURF-AS-

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS20911: 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
AS57344Telehouse EADResidentialIPv43,095
AS174Cogent Communications, LLCTransitIPv41,787
AS9002RETN LimitedUnclassifiedIPv41,593
AS6939Hurricane Electric LLCTransitIPv41,056
AS57463NetIX Communications JSCUnclassifiedIPv4839
AS44901Belcloud LTDHostingIPv4638
AS34549meerfarbig GmbH & Co. KGHostingIPv4352
AS3303Swisscom (Schweiz) AGResidentialIPv4176
AS24482SG.GSHostingIPv4176
AS34019Hivane AssociationUnclassifiedIPv4176

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS8431TEA Ltd.UnclassifiedIPv4245

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv43,210
AS174Cogent Communications, LLCTransitIPv41,787
AS9002RETN LimitedUnclassifiedIPv41,648
AS6939Hurricane Electric LLCTransitIPv41,056
AS57463NetIX Communications JSCUnclassifiedIPv4859
AS44901Belcloud LTDHostingIPv4658
AS34549meerfarbig GmbH & Co. KGHostingIPv4362
AS8431TEA Ltd.UnclassifiedIPv4245
AS24482SG.GSHostingIPv4181
AS37721Virtual Technologies & SolutionsResidentialIPv4181

All 16 adjacent →

Provenance

Where this comes from

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