asn.dev

Observed topology

AS199811 WIFX

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS199811: 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
AS25091IP-Max SAUnclassifiedIPv4 IPv6164
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv670
AS1299Arelion Sweden ABTransitIPv4 IPv654
AS6939Hurricane Electric LLCTransitIPv4 IPv650
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv638
AS24482SG.GSHostingIPv4 IPv67
AS9002RETN LimitedUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203130Haute ecole d ingenierie et de gestion du canton de VaudUnclassifiedIPv4102

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS25091IP-Max SAUnclassifiedIPv4 IPv6214
AS203130Haute ecole d ingenierie et de gestion du canton de VaudUnclassifiedIPv4102
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv690
AS1299Arelion Sweden ABTransitIPv4 IPv668
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS13030Init7 (Switzerland) Ltd.HostingIPv4 IPv647
AS24482SG.GSHostingIPv4 IPv68
AS9002RETN LimitedUnclassifiedIPv64

Provenance

Where this comes from

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